spring-boot/spring-boot-project/spring-boot-tools/spring-boot-gradle-plugin/src/main/gradle/packaging/boot-jar-include-launch-scr...

buildscript {
	dependencies {
		classpath files(pluginClasspath.split(','))
	}
}

apply plugin: 'org.springframework.boot'
apply plugin: 'java'

bootJar {
	mainClassName 'com.example.ExampleApplication'
}

// tag::include-launch-script[]
bootJar {
	launchScript()
}
// end::include-launch-script[]
Provide separate documentation (API and reference) for Gradle plugin 2017-03-15 04:51:23 +08:00			`buildscript {`
			`dependencies {`
			`classpath files(pluginClasspath.split(','))`
			`}`
			`}`

			`apply plugin: 'org.springframework.boot'`
			`apply plugin: 'java'`

			`bootJar {`
Use mainClassName consistently across BootRun, BootJar, and BootWar Previously, BootRun used the main property to configure the name of the main class to run while BootJar and BootWar used the mainClass property. Both were different to the application plugin which provides a mainClassName project property. This commit updates BootRun, BootJar, and BootWar to change the name of the property used to configure the name of the main class to be mainClassName. This makes the three Boot-specific tasks consistent with each other, and also aligns them with Gradle's own application plugin. Closes gh-10622 2017-10-19 19:11:04 +08:00			`mainClassName 'com.example.ExampleApplication'`
Provide separate documentation (API and reference) for Gradle plugin 2017-03-15 04:51:23 +08:00			`}`

			`// tag::include-launch-script[]`
			`bootJar {`
Simply Gradle plugin DSL for configuring a jar or war's launch script Closes gh-9948 2017-09-21 13:55:37 +08:00			`launchScript()`
Provide separate documentation (API and reference) for Gradle plugin 2017-03-15 04:51:23 +08:00			`}`
			`// end::include-launch-script[]`