Avoiding situations where duplicate classnames are imported?

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>