Le vendredi 02 mai 2008, Gilles Scokart a écrit : > By the way, in which case did you need to compare 2 version? > In ivy, we use it mostly for conflict resolution. But maven use a > 'nearest' aproach. So I guess there is no need to compare version > there. > > Is the impact limited to version ranges? This is the only case I'm aware of in Maven Core.
But my need was for m2eclipse, when trying to work on http://jira.codehaus.org/browse/MNGECLIPSE-281. I imagined that Maven's DefaultArtifactVersion was the best way to sort artifacts in m2eclipse consistently with Maven, then discovered how version sorting was broken in Maven... :) Hervé --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
