On 16/10/09 11:47 AM, Stephen Connolly wrote:
2009/10/16 Peter Janes<[email protected]>
However, I'm not aware of any released version of Maven or any plugin that
actually treats dependencies this way; Mercury, tested through
versions-maven-plugin, doesn't appear to either. (But I'd love to be proven
wrong!)
versions-maven-plugin does not use mercury to resolve the artifacts, it only
uses the same comparison rule as mercury uses... artifact resolution is
provided by the maven core that you are running v-m-p with.
Ah, then I did misunderstand the purpose of using the mercury
comparisonMethod. I thought that display-dependency-updates (for example)
would find all of the available versions for the artifact, then compare them
using the Mercury (or Maven, or numeric) rules and find what those rules
considered to be the newest one; now I'm not sure what it's supposed to do
or how.
That does explain why I had a hard time following the source to debug the
processing of LATEST/RELEASE from the repository metadata, though: it was
never there! :)
--
Sometimes the Universe needs a change of perspective.
--J. Michael Straczynski
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
