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
.
- 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
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
Mike Perham wrote:
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
/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
