Commit 0424689a authored by Stephane Nicoll's avatar Stephane Nicoll

Merge branch '2.2.x' into 2.3.x

Closes gh-23930
parents c02b16ee 93e36a97
......@@ -83,12 +83,6 @@ javadoc {
}
}
tasks.withType(org.asciidoctor.gradle.jvm.AbstractAsciidoctorTask) {
attributes "maven-jar-plugin-version": "1.2.3",
"maven-failsafe-plugin-version": "1.2.3",
"build-helper-maven-plugin-version": "1.2.3"
}
task zip(type: Zip) {
dependsOn asciidoctor, asciidoctorPdf
duplicatesStrategy "fail"
......
......@@ -12,7 +12,6 @@ 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>{gradle-project-version}</version>
<executions>
<execution>
<goals>
......
......@@ -14,7 +14,6 @@ To use the Spring Boot Maven Plugin, include the appropriate XML in the `plugins
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
</plugin>
</plugins>
</build>
......
......@@ -10,7 +10,6 @@ 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>{gradle-project-version}</version>
<executions>
<execution>
<id>pre-integration-test</id>
......@@ -63,7 +62,6 @@ The example below showcases how you could achieve the same feature using the htt
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<version>{build-helper-maven-plugin-version}</version>
<executions>
<execution>
<id>reserve-tomcat-port</id>
......@@ -82,7 +80,6 @@ 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>{gradle-project-version}</version>
<executions>
<execution>
<id>pre-integration-test</id>
......@@ -106,7 +103,6 @@ The example below showcases how you could achieve the same feature using the htt
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-failsafe-plugin</artifactId>
<version>{maven-failsafe-plugin-version}</version>
<configuration>
<systemPropertyVariables>
<test.server.port>${tomcat.http.port}</test.server.port>
......@@ -136,7 +132,6 @@ This example shows how you can customize the port in case `9001` is already used
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<jmxPort>9009</jmxPort>
</configuration>
......@@ -187,7 +182,6 @@ 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>{gradle-project-version}</version>
<executions>
<execution>
<id>pre-integration-test</id>
......@@ -212,7 +206,6 @@ This example shows how you can skip integration tests with a command-line proper
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-failsafe-plugin</artifactId>
<version>{maven-failsafe-plugin-version}</version>
<configuration>
<skip>${skip.it}</skip>
</configuration>
......
......@@ -16,7 +16,6 @@ It is possible to automate the creation of an image whenever the `package` phase
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<executions>
<execution>
<goals>
......@@ -131,7 +130,6 @@ If you need to customize the builder used to create the image or the run image u
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<image>
<builder>mine/java-cnb-builder</builder>
......@@ -169,7 +167,6 @@ The following is an example of {paketo-java-reference}/#configuring-the-jvm-vers
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<image>
<env>
......@@ -197,7 +194,6 @@ When using the Paketo builder, this can be accomplished by setting the `HTTPS_PR
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<image>
<env>
......@@ -227,7 +223,6 @@ You can take control over the name, as shown in the following example:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<image>
<name>example.com/library/${project.artifactId}</name>
......
......@@ -12,7 +12,6 @@ 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>{gradle-project-version}</version>
<executions>
<execution>
<goals>
......@@ -48,7 +47,6 @@ The `Main-Class` in the manifest is controlled by the `layout` property of the S
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<mainClass>${start.class}</mainClass>
<layout>ZIP</layout>
......@@ -90,7 +88,6 @@ To use this feature, the layering feature must be enabled:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<layers>
<enabled>true</enabled>
......@@ -128,7 +125,6 @@ This can be done using a separate configuration file that should be registered a
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<layers>
<enabled>true</enabled>
......@@ -225,7 +221,6 @@ 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>{gradle-project-version}</version>
<executions>
<execution>
<id>repackage</id>
......@@ -282,7 +277,6 @@ The following configuration installs/deploys a single `task` classified artifact
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>{maven-jar-plugin-version}</version>
<executions>
<execution>
<goals>
......@@ -298,7 +292,6 @@ The following configuration installs/deploys a single `task` classified artifact
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<executions>
<execution>
<id>repackage</id>
......@@ -368,7 +361,6 @@ 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>{gradle-project-version}</version>
<executions>
<execution>
<id>repackage</id>
......@@ -400,7 +392,6 @@ 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>{gradle-project-version}</version>
<executions>
<execution>
<id>repackage</id>
......@@ -435,7 +426,6 @@ 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>{gradle-project-version}</version>
<executions>
<execution>
<id>repackage</id>
......@@ -492,7 +482,6 @@ The following example excludes `com.foo:bar`, and only that artifact:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<excludes>
<exclude>
......@@ -517,7 +506,6 @@ This example excludes any artifact belonging to the `com.foo` group:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<excludeGroupIds>com.foo</excludeGroupIds>
</configuration>
......@@ -543,7 +531,6 @@ If you wish to exclude this dependency, you can do so in the following manner:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<layers>
<enabled>true</enabled>
......
......@@ -27,7 +27,6 @@ To enable it, just add the following dependency to your project:
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-devtools</artifactId>
<version>{gradle-project-version}</version>
<optional>true</optional>
</dependency>
</dependencies>
......@@ -55,7 +54,6 @@ You can restore it at any time by configuring your project:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<addResources>true</addResources>
</configuration>
......@@ -103,7 +101,6 @@ 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>{gradle-project-version}</version>
<configuration>
<jvmArguments>
-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005
......@@ -140,7 +137,6 @@ The following example sets `property1` to `test` and `property2` to 42:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<systemPropertyVariables>
<property1>test</property1>
......@@ -182,7 +178,6 @@ The following example sets the 'ENV1', 'ENV2', 'ENV3', 'ENV4' env variables:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<environmentVariables>
<ENV1>5000</ENV1>
......@@ -220,7 +215,6 @@ The following example sets two arguments: `property1` and `property2=42`:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<arguments>
<argument>property1</argument>
......@@ -258,7 +252,6 @@ The following configuration enables the `foo` and `bar` profiles:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<profiles>
<profile>foo</profile>
......
......@@ -90,7 +90,7 @@ For instance, to use a different version of the SLF4J library and the Spring Dat
<dependency>
<groupId>org.springframework.data</groupId>
<artifactId>spring-data-releasetrain</artifactId>
<version>Moore-SR6</version>
<version>Neumann-SR5</version>
<type>pom</type>
<scope>import</scope>
</dependency>
......@@ -131,7 +131,6 @@ If you want to both have a default while allowing it to be overridden on the com
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>{gradle-project-version}</version>
<configuration>
<profiles>${app.profiles}</profiles>
</configuration>
......
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