I confirm that the use case you mention is supposed to work transparently. This most likely looks like a bug.
Thanks for reporting this. S. On Fri, Feb 7, 2014 at 3:21 PM, Reto Hablützel <[email protected]> wrote: > Hi there, > > I built an ear using the maven-ear-plugin (version 2.6). > > The ear is configured such that it includes two libraries into the lib > folder, both with the same artifactId as well as the same version, but a > different groupId. Now if I simply call 'mvn package' only the first one is > included, but no warning whatsoever appears. Only once I turn on debugging > (mvn --debug package), I see one subtle message: > [DEBUG] Skipping artifact [jar:com.foo:bar:1.0] as it is already up to date > at [lib/bar-1.0.jar] > > Wouldn't it make sense to either include the groupId in the filename or at > least make a check (that includes the groupId) beforehand if there are any > conflicts? > > Cheers, > Reto >
