As a user of wicket:
+1 for the spring - spring-web change
+1 for the 2.5.6 - 3.0 change. Imho when a new major release of a software
comes out the dependencies should be updated to the latest and greatest
stables.
However even if the version will not get updated I suggest to change 2.5.6
to
+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
-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
-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
if there is no update, will this prevent me to use spring 3 in
On Thu, Feb 17, 2011 at 2:26 PM, Maarten Bosteels
mbosteels@gmail.com wrote:
-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
I use wicket-spring together with Spring 3 in my projects with no problem.
Simply declare your dependency on wicket-spring, along with whatever version of
Spring you desire. Here's an example:
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-spring/artifactId
