I think here is the case of what is happening: A depends on commons-collection 3.0 B depends on A B declares in its dependencyMgmt to use commons-collections 3.1
B's assembly will include commons-collections 3.0 while all other plugins report it depends on 3 I'm going to implement this as a small example to confirm. jaxzin wrote: > > Has anyone else experience the following. > > I run dependency:resolve on my project and it reports that it resolve one > my dependencies to version 1.6.2 but yet when I run the assembly a > different version 1.6.1 is included? How could this possibly be? Don't > they both use the same code to resolve dependency versions? > -- View this message in context: http://www.nabble.com/Assembly-plugin-resolves-dependencies-differently-than-the-dependency-plugin-tp15048075s177p15048929.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
