maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Weber (JIRA)" <>
Subject [jira] Created: (MNG-3248) Specify, which Version in a common Range should be choosen (.e.g.: oldest, newest, ...).
Date Fri, 19 Oct 2007 12:43:52 GMT
Specify, which Version in a common Range should be choosen (.e.g.: oldest, newest, ...).

                 Key: MNG-3248
             Project: Maven 2
          Issue Type: New Feature
          Components: Dependencies
    Affects Versions: 2.0.7
            Reporter: Christian Weber
            Priority: Minor

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

Assuming a Scenario as follows:

 |- LibA
     | - LibC [,]
 |- LibB
     | - LibC [,]

The common Range of the Version of LibC, that match both Requirements is [,].
With the standard Policy, the newest common Version is choosen, as far as i understand. So
in the Scenario, LibC- 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- would be choosen instead.

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:

 |- LibA
     | - LibC [,)
 |- LibB
     | - LibC [,)

Let's say, that i've tested my Programm AppA with LibC 2 Days ago and the Build was
One Day ago a new Version of LibC was released, Version
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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message