Reputation: 1430
Similar to Can I use new spring 3.2 with older spring-security 3.0...
Why does Spring Security not follow the main Spring framework's versioning? I know how Maven dependency management works and that it doesn't strictly have to share the exact same version number, but it's very irritating to have to explicitly exclude the transitive dependencies it declares on old Spring core versions.
Consider the impact of this on a hypotyhetical Spring/Maven newbie: it presents an immediate unshaven haven of Maven raven. Multiple versions of Spring libraries saturating your lib folder, non-deterministic cross-version anomalies, etc.
Quo vadis?
Upvotes: 1
Views: 246
Reputation: 22516
They are different projects. It's the same with Spring Integration, Batch... Imagine that you have to release Spring Security for some small bug. If you keep the versions in sync, than you need to rise the core version just for this...
Upvotes: 2