[
http://jira.codehaus.org/browse/MNG-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-4089:
------------------------------
Assignee: (was: Brett Porter)
> Allow LATEST and RELEASE to peg major version similar to SNAPSHOT
> -----------------------------------------------------------------
>
> Key: MNG-4089
> URL: http://jira.codehaus.org/browse/MNG-4089
> Project: Maven 2 & 3
> Issue Type: Bug
> Reporter: Gin-Ting Chen
>
> 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}
> [RELEASE,25-SNAPSHOT)
> {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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
