I think that depending on the catch all for spring is probably the best for Wicket. If you really want to depend on the individual modules, it is merely a matter of adding excludes to your wicket-spring dependency and including those you do want.
The reason being: most people (at least those that I know) already want to use most of Spring, so there is no reason to exchange 1 dependency for 2, or 3. Because then the majority needs to exclude those 2 (or 3) dependencies from their poms. Martijn On 7/22/07, cwilkes <[EMAIL PROTECTED]> wrote:
Currently the 1.3.0-beta2 version of wicket-parent and wicket-spring depend on the large single "spring" jar. Can this be changed to just depend on the org.springframework artifacts spring-context and spring-web? -- View this message in context: http://www.nabble.com/Can-wicket-spring-just-depend-on-spring-context-and-spring-web--tf4125986.html#a11733423 Sent from the Wicket - Dev mailing list archive at Nabble.com.
-- Wicket joins the Apache Software Foundation as Apache Wicket Apache Wicket 1.3.0-beta2 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/
