Polish
This commit is contained in:
@@ -35,7 +35,8 @@ It also allows you to add an arbitrary number of additional properties, as shown
|
||||
----
|
||||
|
||||
This configuration will generate a `build-info.properties` at the expected location with four additional keys.
|
||||
Note that `maven.compiler.source` and `maven.compiler.target` are expected to be regular properties available in the project.
|
||||
|
||||
NOTE: `maven.compiler.source` and `maven.compiler.target` are expected to be regular properties available in the project.
|
||||
They will be interpolated as you would expect.
|
||||
|
||||
include::goals/build-info.adoc[leveloffset=+1]
|
||||
|
||||
@@ -239,7 +239,7 @@ You can take control over the name, as shown in the following example:
|
||||
</project>
|
||||
----
|
||||
|
||||
Note that this configuration does not provide an explicit tag so `latest` is used.
|
||||
NOTE: This configuration does not provide an explicit tag so `latest` is used.
|
||||
It is possible to specify a tag as well, either using `${project.version}`, any property available in the build or a hardcoded version.
|
||||
|
||||
The image name can be specified on the command line as well, as shown in this example:
|
||||
|
||||
@@ -77,7 +77,8 @@ For more details, see <<repackage-example-exclude-dependency,the dedicated examp
|
||||
Sometimes it is useful to include test dependencies when running the application.
|
||||
For example, if you want to run your application in a test mode that uses stub classes.
|
||||
If you wish to do this, you can set the `useTestClasspath` parameter to true.
|
||||
Note that this is only applied when you run an application: the `repackage` goal will not add test dependencies to the resulting JAR/WAR.
|
||||
|
||||
NOTE: This is only applied when you run an application: the `repackage` goal will not add test dependencies to the resulting JAR/WAR.
|
||||
|
||||
include::goals/run.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ This dependency management lets you omit `<version>` tags for those dependencies
|
||||
* Sensible plugin configuration (https://github.com/ktoso/maven-git-commit-id-plugin[Git commit ID], and https://maven.apache.org/plugins/maven-shade-plugin/[shade]).
|
||||
* Sensible resource filtering for `application.properties` and `application.yml` including profile-specific files (for example, `application-dev.properties` and `application-dev.yml`)
|
||||
|
||||
Note that, since the `application.properties` and `application.yml` files accept Spring style placeholders (`${...}`), the Maven filtering is changed to use `@..@` placeholders.
|
||||
NOTE: Since the `application.properties` and `application.yml` files accept Spring style placeholders (`${...}`), the Maven filtering is changed to use `@..@` placeholders.
|
||||
(You can override that by setting a Maven property called `resource.delimiter`.)
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user