Something like duplicate dependencies likely means you have a real problem you didn't know about in your poms. I think failing is appropriate in this case.
On Thu, Dec 3, 2009 at 5:42 AM, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > 2009/12/3 Stephen Connolly <stephen.alan.conno...@gmail.com> > >> >> >> 2009/12/3 Jorg Heymans <jorg.heym...@gmail.com> >> >>> On Thu, Dec 3, 2009 at 11:10 AM, Stephen Connolly >>> <stephen.alan.conno...@gmail.com> wrote: >>> > 2009/12/3 Jorg Heymans <jorg.heym...@gmail.com> >>> > >>> >> On Tue, Nov 24, 2009 at 12:18 PM, Benjamin Bentmann >>> >> <benjamin.bentm...@udo.edu> wrote: >>> >> > Jorg Heymans wrote: >>> >> > >>> >> >> [ERROR] The project build-tools:1-SNAPSHOT >>> >> >> (D:\src\myproject\pom.xml) has 1 error >>> >> >> [ERROR] >>> >> >> >>> >> >>> 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' >>> >> >> must be unique: junit:junit:jar -> duplicate declaration of version >>> >> >> 3.8.2 >>> >> >> >>> >> >> Shall i log an issue for this or is this a known feature ? >>> >> > >>> >> > The error itself is by design and is part of overall stricter POM >>> >> > validation. If the cause isn't present in the current POM, it must be >>> >> > present in one of its parents. "mvn ... -e" should tell more but I >>> will >>> >> look >>> >> > into improving the message for the next release. >>> >> >>> >> I can understand the need for stricter pom validation, but is it >>> >> really necessary to fail a build completely just because a dependency >>> >> is declared twice ? It seems a bit harsh. >>> > >>> > >>> > Actually, I'm liking this build failing on double dependencies. >>> >>> Any particular reason or do you get a kick out of scanning 60+ module >>> reactor builds for duplicates ? :-P >>> >> >> I've got most of my projects down to no duplicates... the error stops it >> happening again! >> >> Perhaps we should have 2.2.2 start issuing the warning though! Or maybe a >> CLI option for 3.0 such as --no-strict-pom-validation >> > > actually much better is something like > > --yes-i-am-a-bold-developer-and-i-know-i-should-remove-duplicate-dependencies-but-give-me-a-break > > that way you're _encouraged_ to fix it fast > > ;-) > > >> >> >>> >>> Jorg >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >>> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
