Mark Hobson wrote at Freitag, 8. Mai 2009 11:05: > This is really a symptom of the nearest-wins mentality of Maven 2, > since scopes specified in the current POM take precedence over their > transitive values, and not widened as expected. AFAIK Mercury will > replace nearest-wins version conflict resolution with a more usable > highest-wins, so I was hoping that it'd also take a similar approach > with scope conflicts and always widen them, irrespective of where they > are defined. Perhaps Oleg could clarify?
This would be the show stopper for me for ever using Mercury. If I narrow the scope in the local POM it is done *because I want it so*, e.g. preventing compile time deps to a specific implementation that's hidden behind an interface. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
