maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Closed: (MNG-4089) Allow LATEST and RELEASE to peg major version similar to SNAPSHOT
Date Tue, 04 May 2010 11:38:13 GMT


Benjamin Bentmann closed MNG-4089.

    Resolution: Won't Fix
      Assignee: Benjamin Bentmann

The metaversions RELEASE/LATEST are internal constructs that shouldn't be used by users. Also,
MNG-3092 has been fixed so normal version range syntax can be used now.

> Allow LATEST and RELEASE to peg major version similar to SNAPSHOT
> -----------------------------------------------------------------
>                 Key: MNG-4089
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Bug
>            Reporter: Gin-Ting Chen
>            Assignee: Benjamin Bentmann
> If we could do 25-RELEASE/25-LATEST it would provide a huge functionality boost over
the current implementation of these 2 keywords.
> Currently if I use a value range to try to simulate 25-RELEASE (LATEST)
> I would do:
> {code}
> [25,26)
> {code}
> This doesn't work very well as SNAPSHOT would be included for 26 even if no 26 released
versions are.
> Doing:
> {code}
> {code}
> Works slightly better until you release a release version greater than 25 then it again
breaks since it doesn't look at (and can't really be expected to) the numerical comparison
of 25 vs anything higher than it.
> Deploying w. alpha names in versioning will break both these approaches.
> For example: alpha-1.1, beta-1.2, etc

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