If you use an IDE with Maven support it will tell you what version has
been resolved by Maven and will show you the source(s) of the conflict
in your transitive dependencies.
Eclipse/STS is free and includes m2e so you get this solved OOTB with no
additional work required (besides opening the Dependency Hierarchy tab
when reviewing your POM in the editor).
Ron
On 19/01/2015 1:31 AM, Adrien Rivard wrote:
Hi,
if youre artifacts have the same artifactId/groupId/type/classifier it
should'nt happen,Maven should pick only one of the two. If one of
the artifactId/groupId/type/classifier is not the same, it could happen
because it's not the same jar for maven.
On Mon, Jan 19, 2015 at 4:32 AM, Steven Schlansker <
[email protected]> wrote:
Check out
https://github.com/basepom/duplicate-finder-maven-plugin
On Jan 18, 2015, at 6:12 PM, Kevin Burton <[email protected]> wrote:
It looks like I’ve accidentally ended up in a situation where I have
duplicate class names in separate .jars with different versions.
So I’ll have Foo.class in foo-1.0.0.jar and foo-3.0.0.jar …
Shouldn’t Maven fail in this scenario? IE assert that you have
conflicting
dependencies and that you should resolve them by hand.
This usually happens with two projects (usually an older one) depends on
an
older version of a library.
I may be foolishly using a few older libs which, while stable, don’t
really
work with some of their more modern dependencies.
--
Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
<https://plus.google.com/102718274791889610666/posts>
<http://spinn3r.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
