Andy Wilkinson 307fbba9e4 Use spring-boot-dependencies as spring-boot-dependency-tools' parent ... Previously spring-boot-dependency-tools used spring-boot-tools as its parent. This meant that it inherited spring-boot-parents' dependency management that we did not want to expose to applications. The solution to this was to generate the effective pom and then filter out any thing that did not appear in spring-boot-dependencies' pom. This filtering had to unwanted side-effect of breaking bom imports: the effective pom would contain the dependency management from the imported bom, but this would be filtered out as the entries didn't appear in spring-boot-dependencies' pom. This commit updates spring-boot-dependency-tools to use spring-boot-dependencies as its parent. This means that its effective pom contains the desired dependency management and nothing more, allowing the filtering logic to be removed. The use of Spring Security's bom has been reinstated as it will now work as intended and versions for its modules will be available in the CLI and via the Gradle plugin. Closes #825 Fixes #838		2014-05-20 14:33:19 +01:00
..
spring-boot-dependency-tools	Use spring-boot-dependencies as spring-boot-dependency-tools' parent	2014-05-20 14:33:19 +01:00
spring-boot-gradle-plugin	Require single main class	2014-05-16 10:45:17 +01:00
spring-boot-loader	Merge branch '1.0.x'	2014-05-16 14:53:32 +01:00
spring-boot-loader-tools	Require single main class	2014-05-16 10:45:17 +01:00
spring-boot-maven-plugin	Exact match for groupId excludes	2014-05-19 15:39:12 +02:00
pom.xml	Move master to 1.1.0.BUILD-SNAPSHOT	2014-04-24 12:45:20 +01:00