Yes, I have and I don't see any problem. It is impossible to enforce
every artifact in the transitive closure depends on same version of an
artifact. Different artifacts evolve at different pace, while some may
have a dependency on lower versions, some may require higher versions.
It's not just about different versions of same artifact, sometimes
different artifacts may have same classes in them and you may like to
use classes from a particular artifact because that contains the correct
version of classes you are looking for.
More over, we (in GlassFish project) use OSGi, so when someone takes our
artifact, they can always inspect all its dependencies and ensure they
are met in their environment. If they don't ensure, they will get a nice
message that will tell them that desired version of a package is not
available.
I hope you are not defending the unpredictable behavior of maven version
< 2.0.9.
Michael McCallum wrote:
did you ever think that something is seriously wrong if the classpath ordering
causes your build to fail?
That could mean that sometime somewher someone will deploy your application
and use a different order for the jars and it just won't run and the poor
developer/ops person will have no idea...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
