Maven 2 & 3

Make it possible to specify that version should be the LATEST STABLE available

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 2.0.4
  • Fix Version/s: None
  • Component/s: Dependencies
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

Hi!

I've been looking for a way to specify that the latest STABLE version of a library (dependency) should be used automatically. However, I can't seem to find any information on this. Is this not possible? The "Dependency Version Ranges" doesn't solve the problem for me since it sets with the lowest version satisfying the range.

This guy had the same question about a year ago, but it doesn't look promising:
http://www.nabble.com/newbie-ques%3A-downloading-latest-stable-jars-t74577.html#a202750

I asked the same question is this thread:
http://www.nabble.com/How-to-get-the-latest-STABLE-version-of-a-library-dependency-automatical-tf1851718.html

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. MNG-2978 Assembly plugin does not resolve version ranges correctly

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Michael McCallum added a comment -

In order to have a stable system you MUST understand what the latest release means... if you introduce this into your build you have no control over what actually ends up in it. As an end user this is not a huge deal direct except when people start using release in libraries in the main repositories....

you end up using the latest released code of every project and the shit hits the fan

i vote a big -1 for this

Show
Michael McCallum added a comment - In order to have a stable system you MUST understand what the latest release means... if you introduce this into your build you have no control over what actually ends up in it. As an end user this is not a huge deal direct except when people start using release in libraries in the main repositories.... you end up using the latest released code of every project and the shit hits the fan i vote a big -1 for this
Hide
Permalink
Wayne Fay added a comment -

We've talked about this on the User list multiple times. Its just a bad idea. The "latest stable" version of something is not a reproducible element.

Show
Wayne Fay added a comment - We've talked about this on the User list multiple times. Its just a bad idea. The "latest stable" version of something is not a reproducible element.
Hide
Permalink
David J. M. Karlsen added a comment -

Dependency ranges shold be sufficient for this.

Show
David J. M. Karlsen added a comment - Dependency ranges shold be sufficient for this.
Hide
Permalink
David Hoffer added a comment -

What do you mean by 'latest STABLE version of a library"? If you mean latest released version this is what version ranges is supposed to be for. It does bring the latest version into your build, the trouble with it is that it will also consider snapshots to be valid which is a documented bug, see MNG-3092.

Show
David Hoffer added a comment - What do you mean by 'latest STABLE version of a library"? If you mean latest released version this is what version ranges is supposed to be for. It does bring the latest version into your build, the trouble with it is that it will also consider snapshots to be valid which is a documented bug, see MNG-3092 .
Hide
Permalink
Brian Fox added a comment -

We don't really recommend even using LATEST or RELEASE as they introduce enough instability to prevent true reproducibility. The lastest stable is impossible to define.

Show
Brian Fox added a comment - We don't really recommend even using LATEST or RELEASE as they introduce enough instability to prevent true reproducibility. The lastest stable is impossible to define.

People

  • Assignee:
    Unassigned
    Reporter:
    Jimisola Laursen
Vote (9)
Watch (10)

Dates

  • Created:
    Updated:
    Resolved: