Skip to content

S
spring-boot
Commit cbee1631 authored by Andy Wilkinson's avatar Andy Wilkinson
Browse files
Options

Fix version references in Maven Plugin's reference documentation 

Closes gh-19878
parent 331ebe90
Show whitespace changes
Inline Side-by-side
Showing with 19 additions and 19 deletions
spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/docs/asciidoc/build-info.adoc
View file @ cbee1631
......@@ -12,7 +12,7 @@ It also allows you to add an arbitrary number of additional properties, as shown
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<executions>
<execution>
<goals>
......
spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/docs/asciidoc/integration-tests.adoc
View file @ cbee1631
......@@ -11,7 +11,7 @@ To make sure that the lifecycle of your Spring Boot application is properly mana
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<executions>
<execution>
<id>pre-integration-test</id>
......@@ -79,7 +79,7 @@ The example below showcases how you could achieve the same feature using the htt
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<executions>
<execution>
<id>pre-integration-test</id>
......@@ -136,7 +136,7 @@ This example shows how you can skip integration tests with a command-line proper
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<executions>
<execution>
<id>pre-integration-test</id>
......
spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/docs/asciidoc/packaging.adoc
View file @ cbee1631
......@@ -12,7 +12,7 @@ Packaging an executable archive is performed by the `repackage` goal, as shown i
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<executions>
<execution>
<goals>
......@@ -47,7 +47,7 @@ The "Main-Class" in the manifest is actually controlled by the "layout" property
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<configuration>
<mainClass>${start.class}</mainClass>
<layout>ZIP</layout>
......@@ -92,7 +92,7 @@ If that is the case or if you prefer to keep the original artifact and attach th
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<executions>
<execution>
<id>repackage</id>
......@@ -165,7 +165,7 @@ The following configuration installs/deploys a single `task` classified artifact
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<executions>
<execution>
<id>repackage</id>
......@@ -235,7 +235,7 @@ If you need the repackaged jar to have a different local name than the one defin
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<executions>
<execution>
<id>repackage</id>
......@@ -267,7 +267,7 @@ If you need to only deploy the original jar and yet be able to run your app with
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<executions>
<execution>
<id>repackage</id>
......@@ -302,7 +302,7 @@ Spring Boot repackages the jar file for this project using a custom layout facto
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<executions>
<execution>
<id>repackage</id>
......@@ -359,7 +359,7 @@ The following example excludes `com.foo:bar`, and only that artifact:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<configuration>
<excludes>
<exclude>
......@@ -384,7 +384,7 @@ This example excludes any artifact belonging to the `com.foo` group:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<configuration>
<excludeGroupIds>com.foo</excludeGroupIds>
</configuration>
......
spring-boot-project/spring-boot-tools/spring-boot-maven-plugin/src/docs/asciidoc/running.adoc
View file @ cbee1631
......@@ -26,7 +26,7 @@ To enable it, just add the following dependency to your project:
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-devtools</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<optional>true</optional>
</dependency>
</dependencies>
......@@ -54,7 +54,7 @@ You can restore it at any time by configuring your project:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<configuration>
<addResources>true</addResources>
</configuration>
......@@ -99,7 +99,7 @@ The following configuration suspend the process until a debugger has joined on p
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<configuration>
<jvmArguments>
-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005
......@@ -136,7 +136,7 @@ The following example sets `property1` to `test` and `property2` to 42:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<configuration>
<systemPropertyVariables>
<property1>test</property1>
......@@ -178,7 +178,7 @@ The following example sets the 'ENV1', 'ENV2', 'ENV3', 'ENV4' env variables:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<configuration>
<environmentVariables>
<ENV1>5000</ENV1>
......@@ -217,7 +217,7 @@ The following configuration enables the `foo` and `bar` profiles:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{version}</version>
<version>{gradle-project-version}</version>
<configuration>
<profiles>
<profile>foo</profile>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment