GitHub-Spring/spring-framework - spring-framework - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Brian Clozel	afcc430481	Remove dependency management noise from POMs Prior to this commit, the generated POMs for Spring Framework modules would contain unneeded/harmful information from the Spring Framework build: 1. The BOM imports applied to each module by the dependency management plugin, for example for Netty or Reactor Netty. Spring should not export that opinion to its POMs. 2. The exclusion of "org.slf4:jcl-over-slf4j" from all dependencies, which made the POMs much larger than necessary and suggested to developers that they should exclude it as well when using all those listed dependencies. In fact, only Apache Tiles currently brings that transitively. This commit removes that information from the POMs. The dependencyManagement Gradle plugin is disabled for POM generation and we manually resolve the dependency versions during the generation phase. The Gradle build is streamlined to exclude "org.slf4:jcl-over-slf4j" only when necessary. Issue: SPR-16893 (Cherry-picked from 417354da8a)	8 years ago
Juergen Hoeller	9190b76ab9	Latest dependency updates (POI 3.17, Rome 1.8, EhCache 3.4, Caffeine 2.5.6, RxJava 2.1.4, Tomcat 8.5.21, JRuby 9.1.13, Rhino 1.7.7.2)	9 years ago
Brian Clozel	cc3d7d2d48	Apply dependency management to selected modules This commit applies the Dependency Management Plugin to modules that require it; right now Spring Framework is importing BOMs for Netty and Reactor dependencies only. Instead of applying those BOMs to all modules, they're applied only where they're needed. Issue: SPR-15885	9 years ago
Brian Clozel	2eeb428e95	Move modules to independent build files The main `build.gradle` file contains now only the common build infrastructure; all module-specific build configurations have been moved to their own build file. Issue: SPR-15885	9 years ago