James Carman a écrit :
I just tried a test by putting in commons-collections 3.1 and 3.2 as dependencies. When I listed the dependencies (using the maven plugin), I only see 3.2. So, I guess we have to change the artifact id too.
That's slightly different since both artifacts are in the same commons-collection group. Tomorrow if a project depends on the artifacts commons-configuration 1.5 (in the commons-configuration group) and commons-configuration 2.0 (in the org.apache.commons group), Maven will use both artifacts I think, and not only the latest revision. Thus renaming the artifact doesn't seem necessary to me, but I may be missing something.
Emmanuel Bourg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
