Skip to content

Commit edf31ca

Browse files
committed
resolves #943
1 parent 4d9e347 commit edf31ca

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

docs/modules/ROOT/pages/batch.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ this section.
1313
[[batch-association]]
1414
== Associating a Job Execution to the Task in which It Was Executed
1515

16-
Spring Boot provides facilities for the execution of batch jobs within an über-jar.
16+
Spring Boot provides facilities for the execution of batch jobs within a Spring Boot Uber-jar.
1717
Spring Boot's support of this functionality lets a developer execute multiple batch jobs
1818
within that execution. Spring Cloud Task provides the ability to associate the execution
1919
of a job (a job execution) with a task's execution so that one can be traced back to the
@@ -62,7 +62,7 @@ most cloud infrastructures. The `DeployerPartitionHandler` and
6262
Cloud Deployer.
6363

6464
To configure the `DeployerStepExecutionHandler`, you must provide a `Resource`
65-
representing the Spring Boot über-jar to be executed, a `TaskLauncherHandler`, and a
65+
representing the Spring Boot Uber-jar to be executed, a `TaskLauncherHandler`, and a
6666
`JobExplorer`. You can configure any environment properties as well as the max number of
6767
workers to be executing at once, the interval to poll for the results (defaults to 10
6868
seconds), and a timeout (defaults to -1 or no timeout). The following example shows how
@@ -111,10 +111,10 @@ Notice in the example above that we have set the maximum number of workers to 2.
111111
Setting the maximum of workers establishes the maximum number of
112112
partitions that should be running at one time.
113113

114-
The `Resource` to be executed is expected to be a Spring Boot über-jar with a
114+
The `Resource` to be executed is expected to be a Spring Boot Uber-jar with a
115115
`DeployerStepExecutionHandler` configured as a `CommandLineRunner` in the current context.
116116
The repository enumerated in the preceding example should be the remote repository in
117-
which the über-jar is located. Both the manager and worker are expected to have visibility
117+
which the Spring Boot Uber-jar is located. Both the manager and worker are expected to have visibility
118118
into the same data store being used as the job repository and task repository. Once the
119119
underlying infrastructure has bootstrapped the Spring Boot jar and Spring Boot has
120120
launched the `DeployerStepExecutionHandler`, the step handler executes the requested

docs/modules/ROOT/pages/stream.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ shown in the following example:
5454
`mvn clean install`
5555

5656
NOTE: The `maven.remoteRepositories.springRepo.url` property must be set to the location
57-
of the remote repository in which the über-jar is located. If not set, there is no remote
57+
of the remote repository in which the Spring Boot Uber-jar is located. If not set, there is no remote
5858
repository, so it relies upon the local repository only.
5959

6060
[[stream-integration-launching-sink-dataflow]]

0 commit comments

Comments
 (0)