I think you should keep the dependency on the 2.5 version, unless new features actually add something *to the wicket-spring module*.
But I'd welcome the change from 'spring' to 'spring-web', since it actually lowers the library dependency. I know you guys like to upgrade library versions (like you did with servlet-api, even if all the tests pass with 2.3), but my preference is to always minimize requirements on dependencies. Tetsuo On Wed, Feb 16, 2011 at 1:11 PM, Martijn Dashorst <martijn.dasho...@gmail.com> 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 > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com >
