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> <groupId>org.apache.wicket</groupId> <artifactId>wicket-spring</artifactId> <version>1.4.15</version> </dependency> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-web</artifactId> <version>3.0.5.RELEASE</version> </dependency> This combination works fine for me. In fact, it doesn't really matter what artifact or version of Spring is listed in the wicket-spring POM, because the Spring dependency is declared as <scope>provided</scope>. This means it will not be included in your application. Contrary to the OP, I don't think a conflict is possible. Here's what the wicket-spring POM looks like now: <dependency> <groupId>org.springframework</groupId> <artifactId>spring</artifactId> <scope>provided</scope> </dependency> From the maven docs: "[The provided scope] is only available on the compilation and test classpath, and **is not transitive.**" (Emphasis mine) However, purely from a documentation standpoint, I agree it would be better to declare explicitly the module of Spring that wicket-spring requires (i.e. "spring-web") rather than the all-in-one "spring" artifact. -- Matt On Feb 17, 2011, at 12:06 PM, Christian Grobmeier 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 >> wicket-spring > > if there is no update, will this prevent me to use spring 3 in my project?
