I have two dependencies in my project that both depend on different versions of commons-collections.
OpenJPA -> commons-collections 3.2 Wicket 2.0 -> commons-collections 2.1 Wicket seems to 'win' and commons-collections 2.1 is included. Unfortunately this does not work for OpenJPA so I had to add a dependency to commons-collections 3.1 to my project. That seemed to override the choice. Is there a better way to do this? If I know that commons-collections always guarantees backward compatibility, is it possible to change the dependency in Wicket to 'commons collections 2.1 or higher' ? Can Maven2 do that and will that help resolving the right version in this case? S. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
