This has been discussed over and over. In our experience most people want to use the whole. And if not, then they *ONLY* need to exclude one dependency, whereas otherwise they have to do a lot more.
We have made a conscious decision to use spring instead of spring-*. Martijn On 10/17/07, Alex Objelean <[EMAIL PROTECTED]> wrote: > > In parent/pom.xml there is a dependency on spring-2.0. I most of the > projects, it is a best practice to not use the entire spring as a > dependency, but to use modular dependencies (eg: spring-core, spring-web, > etc). > > For instance, now you depend on spring-2.0 and the project we are building > is depending on spring-core-2.0.7. When maven builds the war, the classpath > contains both: spring-2.0 & spring-core-2.0.7 which is causing some troubles > depending on working environment. > > Thanks! > Alex. > -- > View this message in context: > http://www.nabble.com/-RFE--Transitive-dependencies-changes-in-parent-pom.xml-tf4640092.html#a13252196 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0-beta4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
