-1 for updating to spring 3 (especially when wicket-spring doesn't need features not available in 2.5.6)
How about <version>[2.5.6,)</version> ? It clearly indicates that 2.5.6 is the minimum required version for wicket-spring http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges Maarten On Thu, Feb 17, 2011 at 1:16 PM, Daniel Soneira <daniel.sone...@joyn-it.at>wrote: > +1 for only depending on spring-web (if that also exists in 2.5) > -1 for updating to spring 3 > > I don't think you depend on any specific feature for wicket-spring that is > only available in that particular version. > I'm also one of the guys who is quick on the update of libraries but I'm > not developing a framework like you do. > The dependency update on servlet API 2.5 I could somehow understand seeing > it really is out for quite some time now. > That argument does not apply to Spring 3 IMHO though. > > -Daniel > > > On 16.02.2011 16:11, Martijn Dashorst wrote: > >> Currently wicket-spring 1.5 depends on spring 2.5 (specifically >> org.springframework:spring:2.5.x:jar) which collides when folks are >> upgrading to spring 3, since spring 3 doesn't have an aggregate >> library any more. >> >> If we chose to upgrade to spring 3, should we depend on spring-web or >> spring-core? >> >> Martijn >> >>
