Mark Hobson wrote:
I haven't pursued this of recent since there was talk of overhauling
maven-artifact and the whole dependency resolution mechanism in
general with Mercury:
http://docs.codehaus.org/display/MAVEN/Mercury
AFAIK Mercury will supersede MNG-612 and provide customisable conflict
resolvers, although I am not aware of the details. Perhaps Oleg could
confirm this and put both our minds at rest? :)
You can safely put your minds at rest guys :)
Mercury is a customizable conflict resolver in a sense that:
- it's a standalone library with no Maven dependencies
- you can supply your own dependency provider - it does not depend on
POM files. Shane wrote an adaptor for ProjectBuilder which reads POMs
- it still operates on GAV model, so all the benefits/problems apply
- SNAPSHOT, RELEASE, LATEST are supported
- it implemented OSGi standard version ranges
- single version behavior is configurable: can be either x=1.2.3 by
default, or could be x>=1.2.3 with an option
- version range interpreter could be replaced - as it's an interface
- SAT conflict resolver itself is hardwired for now, but I can
externalize it as well
Dis I answer all questions? Ask more :)
Thanks,
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
