[MNG-3248] Specify, which Version in a common Range should be choosen (.e.g.: oldest, newest, ...).

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.0.7
• Component/s: Dependencies
• Assignee: Brett Porter
• Reporter: Chris Wojdak
• Created: 19/Oct/07 07:42
• Updated: 29/Oct/07 20:50
• Resolved: 29/Oct/07 20:50

Description

I want to propose Feature according the Policy of Choosing a specific Version in a common Range.

Assuming a Scenario as follows:

AppA

LibA

LibC [1.4.0.7,1.4.0.15]

LibB

LibC [1.4.0.4,1.4.0.13]

The common Range of the Version of LibC, that match both Requirements is [1.4.0.7,1.4.0.13].
With the standard Policy, the newest common Version is choosen, as far as i understand. So in the Scenario, LibC-1.4.0.13 is choosen.
It would be also useful to be able to instruct Maven to always choose the oldest common Version, so that in the Scenario, LibC-1.4.0.7 would be choosen instead.

Example:
This Way it is much more suitable for testing, because i can reproduce a specific Build, no matter how many new Version were released in the Meantime.
Let me explain, why i need this with Szenario 2:

AppA

LibA

LibC [1.4.0.9,)

LibB

LibC [1.4.0.8,)

Let's say, that i've tested my Programm AppA with LibC 1.4.0.8 2 Days ago and the Build was successfull.
One Day ago a new Version of LibC was released, Version 1.5.0.0.
If i now start the same Build Process, it will most problably fail.
If Maven would would have always choosen the oldest common Version, the Build would have succeeded, assuming that i didn't change AppA.
This would be the Scenario of Testing a specific Build and deploying it some Days later.

Issue Links

• duplicates: MNG-612 implement conflict resolution techniques