spring-boot/spring-boot-tools
Andy Wilkinson 8673250955 Make use of Gradle's application plugin optional when using Boot plugin
Previously, the Spring Boot Gradle plugin would always apply the
application plugin to a project. It then piggy-backed on the application
plugin’s mainClassName and applicationDefaultJvmArgs properties for the
configuration of the bootRun task.

This commit updates the Spring Boot Gradle plugin so that it no longer
applies the application plugin. If the user applies the application
plugin then its configuration will be used, but it’s a no longer
requirement.

Users who do not need the application plugin, but who were using the
mainClassName or applicationDefaultJvmArgs properties will need to
change their builds as a result of this change as those properties will
no longer exist. As before, the mainClassName can be configured on the
springBoot extension:

springBoot {
	mainClassName 'com.example.YourApplication'
}

The applicationDefaultJvmArgs property can be used, but it must now be
declared with the project's ext block. For example:

ext {
	applicationDefaultJvmArgs = [ '-Dcom.example.property=true' ]
}

Closes gh-2679
2015-07-22 11:38:15 +01:00
..
spring-boot-antlib Create spring-boot-antlib module 2015-06-30 00:30:28 -07:00
spring-boot-configuration-metadata Polish 2015-07-16 12:56:49 -07:00
spring-boot-configuration-processor Add @DeprecatedConfigurationProperties annotation 2015-07-17 14:14:37 -07:00
spring-boot-gradle-plugin Make use of Gradle's application plugin optional when using Boot plugin 2015-07-22 11:38:15 +01:00
spring-boot-loader Add missing jar (.gitignored) 2015-07-14 12:44:23 +01:00
spring-boot-loader-tools Fix typos 2015-07-15 15:45:02 +02:00
spring-boot-maven-plugin Remove unnecessary keyword 2015-07-09 14:33:01 +02:00
pom.xml Add configuration meta-data parser 2015-07-13 11:53:31 +02:00