Andy Wilkinson 4be688aa78 Fix Gradle repackaging so it is only performed on the desired jars ... The logic that determined whether or not the repackaging action should be applied to a particular jar task was broken and caused problems when a custom RepackageTask was used in a project's build. This commit updates the logic so that repackaging will be applied: - To the default jar task if RepackageTask.withJarTask is null - To a jar task if it is equal to RepackageTask.withJarTask - To a jar task if its name is equal to RepackageTask.withJarTask Repackaging is not applied if: - RepackageTask.enabled is false Numerous integration tests have been added to verify the repackaging behaviour. Fixes #1204		2014-07-03 11:42:11 +01:00
..
spring-boot-dependency-tools	Remote trailing whitespace	2014-07-02 15:17:14 -07:00
spring-boot-gradle-plugin	Fix Gradle repackaging so it is only performed on the desired jars	2014-07-03 11:42:11 +01:00
spring-boot-loader	Remote trailing whitespace	2014-07-02 15:17:14 -07:00
spring-boot-loader-tools	Remote trailing whitespace	2014-07-02 15:17:14 -07:00
spring-boot-maven-plugin	Remote trailing whitespace	2014-07-02 15:17:14 -07:00
pom.xml	Next development version	2014-06-26 14:09:54 -07:00