Clarify docs on app registration and use of --force (#2987)

Author: Mark Pollack

spring-cloud-dataflow-docs/src/main/asciidoc/getting-started-cloudfoundry.adoc

@@ -365,10 +365,10 @@ The goal is to perform a rolling upgrade of the `log-sink` application to `1.2.0
 
 [source,console,options=nowrap]
 ----
-dataflow:>app register --name time --type source --uri maven://org.springframework.cloud.stream.app:time-source-rabbit:1.2.0.RELEASE --force
+dataflow:>app register --name time --type source --uri maven://org.springframework.cloud.stream.app:time-source-rabbit:1.2.0.RELEASE
 Successfully registered application 'source:time'
 
-dataflow:>app register --name log --type sink --uri maven://org.springframework.cloud.stream.app:log-sink-rabbit:1.1.0.RELEASE --force
+dataflow:>app register --name log --type sink --uri maven://org.springframework.cloud.stream.app:log-sink-rabbit:1.1.0.RELEASE
 Successfully registered application 'sink:log'
 
 dataflow:>app info source:time
@@ -501,7 +501,7 @@ Now you can update `log-sink` from `1.1.0.RELEASE` to `1.2.0.RELEASE`.  First we
 
 [source,console,options=nowrap]
 ----
-dataflow:>app register --name log --type sink --uri maven://org.springframework.cloud.stream.app:log-sink-rabbit:1.1.0.RELEASE --force
+dataflow:>app register --name log --type sink --uri maven://org.springframework.cloud.stream.app:log-sink-rabbit:1.1.0.RELEASE
 Successfully registered application 'sink:log'
 ----
 

spring-cloud-dataflow-docs/src/main/asciidoc/getting-started-kubernetes.adoc

@@ -949,7 +949,7 @@ The following example (with output after each command) shows how to register the
 
 [source,console,options=nowrap]
 ----
-dataflow:>app register --name log --type sink --uri docker:springcloudstream/log-sink-rabbit:2.1.0.RELEASE --force
+dataflow:>app register --name log --type sink --uri docker:springcloudstream/log-sink-rabbit:2.1.0.RELEASE
 Successfully registered application 'sink:log'
 
 dataflow:>stream update --name mystream --properties version.log=2.1.0.RELEASE

spring-cloud-dataflow-docs/src/main/asciidoc/getting-started-local.adoc

@@ -279,7 +279,7 @@ Now you can use the `maven://` URI schema and maven coordinates to resolve jars
 
 [source,bash,subs=attributes]
 ----
-dataflow:>app register --type processor --name pose-estimation --uri maven://org.springframework.cloud.stream.app:pose-estimation-processor-rabbit:2.0.2.BUILD-SNAPSHOT --metadata-uri maven://org.springframework.cloud.stream.app:pose-estimation-processor-rabbit:jar:metadata:2.0.2.BUILD-SNAPSHOT --force
+dataflow:>app register --type processor --name pose-estimation --uri maven://org.springframework.cloud.stream.app:pose-estimation-processor-rabbit:2.0.2.BUILD-SNAPSHOT --metadata-uri maven://org.springframework.cloud.stream.app:pose-estimation-processor-rabbit:jar:metadata:2.0.2.BUILD-SNAPSHOT
 ----
 
 This approach allow you to share jars build and installed on the host machine (e.g. `mvn clean install`) directly with the dataflow-server container.

spring-cloud-dataflow-docs/src/main/asciidoc/streams.adoc

@@ -465,8 +465,8 @@ be resolved from the Data Flow Server process, specify `--local false`.
 [WARNING]
 ====
 When using either `app register` or `app import`, if an app is already registered with
-the provided name and type, it is not overridden by default. If you would like to override the
-pre-existing app coordinates, then include the `--force` option.
+the provided name and type and version, it is not overridden by default. If you would like to override the
+pre-existing app uri or metadata-uri coordinates, then include the `--force` option.
 
 Note, however, that, once downloaded, applications may be cached locally on the Data Flow server, based on the resource
 location. If the resource location does not change (even though the actual resource _bytes_ may be different), then it

spring-cloud-dataflow-docs/src/main/asciidoc/tasks.adoc

@@ -132,8 +132,8 @@ You can also pass the `--local` option (which is `TRUE` by default) to indicate
 If the location should be resolved from the Data Flow Server process, specify `--local false`.
 
 When using either `app register` or `app import`, if a task app is already registered with
-the provided name, it is not overridden by default. If you would like to override the
-pre-existing task app, then include the `--force` option.
+the provided name and version, it is not overridden by default. If you would like to override the
+pre-existing task app with a different uri or uri-metadata location, then include the `--force` option.
 
 [NOTE]
 In some cases, the Resource is resolved on the server side.