[MNG-4089] Allow LATEST and RELEASE to peg major version similar to SNAPSHOT

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Assignee: Benjamin Bentmann
• Reporter: Tim Chen
• Created: 16/Mar/09 12:45
• Updated: 04/May/10 06:37
• Resolved: 04/May/10 06:37

Description

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:

[25,26)

This doesn't work very well as SNAPSHOT would be included for 26 even if no 26 released versions are.
Doing:

[RELEASE,25-SNAPSHOT)

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

Issue Links

• duplicates: MNG-3092 Resolution of version ranges with non-snapshot bounds can resolve to a snapshot version