Fix typos in new Gradle plugin

Closes gh-8818
pull/7469/head
Johnny Lim 8 years ago committed by Andy Wilkinson
parent 2de7e9c310
commit 8d921d49aa

@ -2818,7 +2818,7 @@ And if you're using Gradle:
}
----
NOTE: `providedRuntime` is prefered to Gradle's `compileOnly` configuration as, among other
NOTE: `providedRuntime` is preferred to Gradle's `compileOnly` configuration as, among other
limitations, `compileOnly` dependencies are not on the test classpath so any web-based
integration tests will fail.

@ -16,7 +16,7 @@ include::../gradle/integrating-with-actuator/build-info-basic.gradle[tags=build-
----
This will configure a {build-info-javadoc}[`BuildInfo`] task named `bootBuildInfo` and, if
it exists, make the Java plugin's `classes` task depend upon it. The task's desination
it exists, make the Java plugin's `classes` task depend upon it. The task's destination
directory will be `META-INF` in the output directory of the main source set's resources
(typically `build/resources/main`).

@ -37,7 +37,7 @@ include::../gradle/packaging/war-container-dependency.gradle[tags=dependencies]
This ensures that they are package in the war file's `WEB-INF/lib-provided` directory
from where they will not conflict with the external container's own classes.
NOTE: `providedRuntime` is prefered to Gradle's `compileOnly` configuration as, among
NOTE: `providedRuntime` is preferred to Gradle's `compileOnly` configuration as, among
other limitations, `compileOnly` dependencies are not on the test classpath so any
web-based integration tests will fail.
@ -60,7 +60,7 @@ By default, the executable archive's main class will be configured automatically
looking for a class with a `public static void main(String[])` method in directories on
the task's classpath.
The main class can also be configured explicity using the task's `mainClass` property:
The main class can also be configured explicitly using the task's `mainClass` property:
[source,groovy,indent=0,subs="verbatim"]
----

@ -34,7 +34,7 @@ include::../gradle/publishing/maven-publish.gradle[tags=publishing]
[[publishing-your-application-distrubution]]
[[publishing-your-application-distribution]]
=== Distributing with the `application` plugin
When the {application-plugin}[`application` plugin] is applied a distribution named

@ -17,7 +17,7 @@ the runtime classpath of the main source set.
By default, the main class will be configured automatically by looking for a class with a
`public static void main(String[])` method in directories on the task's classpath.
The main class can also be configured explicity using the task's `main` property:
The main class can also be configured explicitly using the task's `main` property:
[source,groovy,indent=0,subs="verbatim"]
----

@ -42,7 +42,7 @@ public class SpringBootPlugin implements Plugin<Project> {
*
* @since 2.0.0
*/
public static final String BOOT_ARCHIVES_CONFIURATION_NAME = "bootArchives";
public static final String BOOT_ARCHIVES_CONFIGURATION_NAME = "bootArchives";
/**
* The name of the {@link SoftwareComponent} for a Spring Boot Java application.
@ -76,7 +76,7 @@ public class SpringBootPlugin implements Plugin<Project> {
public void apply(Project project) {
project.getExtensions().create("springBoot", SpringBootExtension.class, project);
Configuration bootArchives = project.getConfigurations()
.create(BOOT_ARCHIVES_CONFIURATION_NAME);
.create(BOOT_ARCHIVES_CONFIGURATION_NAME);
SinglePublishedArtifact singlePublishedArtifact = new SinglePublishedArtifact(
bootArchives.getArtifacts());
List<PluginApplicationAction> actions = Arrays.asList(

@ -64,7 +64,7 @@ public class ApplicationPluginActionIntegrationTests {
}
@Test
public void applyingApplictionPluginCreatesBootStartScriptsTask() {
public void applyingApplicationPluginCreatesBootStartScriptsTask() {
assertThat(this.gradleBuild.build("taskExists", "-PtaskName=bootStartScripts",
"-PapplyApplicationPlugin").getOutput())
.contains("bootStartScripts exists = true");

Loading…
Cancel
Save