That's too bad. I think deps at the same level should pick the greater, not randomly. MNG-1577 would help a lot here.
I'm also finding that exclusions are insideous - I can't see where an exclusion is coming from so I can't determine which module is erroneously excluding a dep I need. On 9/18/06, Brett Porter <[EMAIL PROTECTED]> wrote:
It doesn't pick randomly, it picks based on nearest, which is undefined if there are two at the same level. However, this was mucked with in 2.0.4 and seemed to get a bit worse. I originally had it set to greater and there was much confusion because you couldn't always see where the version was coming from (you expected one, got another because it was "less visible"). I think now that transitive deps are more familiar, this probably would be received better. The plan was always to (re-)introduce the conflict resolution strategies to make this configurable in Maven 2.1. - Brett On 19/09/2006, at 12:58 AM, Mike Perham wrote: > We constantly have version selection problems where Maven's random > version selection bites us. This would almost always be solved if > Maven would select the greater of the two versions. Why doesn't Maven > do this instead of picking randomly? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
