You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gin-Ting Chen (JIRA)" <ji...@codehaus.org> on 2009/03/16 18:46:12 UTC
[jira] Created: (MNG-4089) Allow LATEST and RELEASE to peg major
version similar to SNAPSHOT
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
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
[jira] Updated: (MNG-4089) Allow LATEST and RELEASE to peg major
version similar to SNAPSHOT
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Reopened: (MNG-4089) Allow LATEST and RELEASE to peg major
version similar to SNAPSHOT
Posted by "Gin-Ting Chen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gin-Ting Chen reopened MNG-4089:
--------------------------------
This is not a duplicate of the linked issue. It's a completely different (simpler) mechanism and allows locking to a feature stream.
> 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
> Issue Type: Bug
> Reporter: Gin-Ting Chen
> Assignee: Brett Porter
>
> 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
[jira] Closed: (MNG-4089) Allow LATEST and RELEASE to peg major
version similar to SNAPSHOT
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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: http://jira.codehaus.org/browse/MNG-4089
> 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}
> [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
[jira] Closed: (MNG-4089) Allow LATEST and RELEASE to peg major
version similar to SNAPSHOT
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-4089.
-----------------------------
Assignee: Brett Porter
Resolution: Duplicate
> 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
> Issue Type: Bug
> Reporter: Gin-Ting Chen
> Assignee: Brett Porter
>
> 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