diff --git a/spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/docs/asciidoc/publishing.adoc b/spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/docs/asciidoc/publishing.adoc index 5bb1e97017..5e81ff2e14 100644 --- a/spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/docs/asciidoc/publishing.adoc +++ b/spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/docs/asciidoc/publishing.adoc @@ -4,7 +4,7 @@ [[publishing-your-application-maven]] -=== Publishing with the Maven Plugin +=== Publishing with the `maven` Plugin When the {maven-plugin}[`maven` plugin] is applied, an `Upload` task for the `bootArchives` configuration named `uploadBootArchives` is automatically created. By default, the `bootArchives` configuration contains the archive produced by the `bootJar` or `bootWar` task. The `uploadBootArchives` task can be configured to publish the archive to a Maven repository: @@ -24,7 +24,7 @@ include::../gradle/publishing/maven.gradle.kts[tags=upload] [[publishing-your-application-maven-publish]] -=== Publishing with the Maven-publish Plugin +=== Publishing with the `maven-publish` Plugin To publish your Spring Boot jar or war, add it to the publication using the `artifact` method on `MavenPublication`. Pass the task that produces that artifact that you wish to publish to the `artifact` method. For example, to publish the artifact produced by the default `bootJar` task: @@ -44,7 +44,7 @@ include::../gradle/publishing/maven-publish.gradle.kts[tags=publishing] [[publishing-your-application-distribution]] -=== Distributing with the Application Plugin +=== Distributing with the `application` Plugin When the {application-plugin}[`application` plugin] is applied a distribution named `boot` is created. This distribution contains the archive produced by the `bootJar` or `bootWar` task and scripts to launch it on Unix-like platforms and Windows. Zip and tar distributions can be built by the `bootDistZip` and `bootDistTar` tasks respectively. diff --git a/spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/docs/asciidoc/reacting.adoc b/spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/docs/asciidoc/reacting.adoc index 0ba6b1f72e..6adeebefc5 100644 --- a/spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/docs/asciidoc/reacting.adoc +++ b/spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/docs/asciidoc/reacting.adoc @@ -6,7 +6,7 @@ This section describes those changes. [[reacting-to-other-plugins-java]] -=== Reacting to the Java Plugin +=== Reacting to the `java` Plugin When Gradle's {java-plugin}[`java` plugin] is applied to a project, the Spring Boot plugin: 1. Creates a {boot-jar-javadoc}[`BootJar`] task named `bootJar` that will create an executable, fat jar for the project. @@ -32,7 +32,7 @@ When {kotlin-plugin}[Kotlin's Gradle plugin] is applied to a project, the Spring [[reacting-to-other-plugins-war]] -=== Reacting to the War Plugin +=== Reacting to the `war` Plugin When Gradle's {war-plugin}[`war` plugin] is applied to a project, the Spring Boot plugin: 1. Creates a {boot-war-javadoc}[`BootWar`] task named `bootWar` that will create an executable, fat war for the project. @@ -50,7 +50,7 @@ When the {dependency-management-plugin}[`io.spring.dependency-management` plugin [[reacting-to-other-plugins-application]] -=== Reacting to the Application Plugin +=== Reacting to the `application` Plugin When Gradle's {application-plugin}[`application` plugin] is applied to a project, the Spring Boot plugin: 1. Creates a `CreateStartScripts` task named `bootStartScripts` that will create scripts that launch the artifact in the `bootArchives` configuration using `java -jar`. @@ -64,5 +64,5 @@ When Gradle's {application-plugin}[`application` plugin] is applied to a project [[reacting-to-other-plugins-maven]] -=== Reacting to the Maven plugin +=== Reacting to the `maven` plugin When Gradle's {maven-plugin}[`maven` plugin] is applied to a project, the Spring Boot plugin will configure the `uploadBootArchives` `Upload` task to ensure that no dependencies are declared in the pom that it generates.