I cannot find use cases where asking for g:a:LATEST is different from
g:a:RELEASE, so I merge these two in Mercury.
Please comment in
http://docs.codehaus.org/display/MAVEN/Mercury+Repository+Abstraction#MercuryRepositoryAbstraction-ArtifactVersionsspecialtreatment
LATEST was intended to refer to the latest regardless of whether it
was a snapshot or release. RELEASE is the latest non-snapshot.
You found no evidence of that being used?
On 20-Aug-08, at 3:47 PM, Oleg Gusakov wrote:
I cannot find use cases where asking for g:a:LATEST is different
from
I did not find RELEASE.
Thanks for the clarification, I will document implement the meanings
described.
Oleg
Jason van Zyl wrote:
LATEST was intended to refer to the latest regardless of whether it
was a snapshot or release. RELEASE is the latest non-snapshot.
You found no evidence of
The requested changes documented on the same page.
Please feel free to comment there if there are any other special
versions we'd like to see.
Jason van Zyl wrote:
LATEST was intended to refer to the latest regardless of whether it
was a snapshot or release. RELEASE is the latest
On Thu, 21 Aug 2008 10:47:04 Oleg Gusakov wrote:
I cannot find use cases where asking for g:a:LATEST is different from
g:a:RELEASE, so I merge these two in Mercury.
Please comment in
http://docs.codehaus.org/display/MAVEN/Mercury+Repository+Abstraction#Mercu
The use case was for plugins (to have snapshots so you grab the ones
you are developing).
We're way better off requiring you ask for that somewhere, so I think
LATEST can go. I'd consider if RELEASE is even needed if you can use
ranges for it effectively.
- Brett
On 21/08/2008, at 9:13
Reverted back and implemented as Jason indicated in his reply. Changes
reflected in documentation.
LATEST was intended to refer to the latest regardless of whether it
was a snapshot or release. RELEASE is the latest non-snapshot.
Michael McCallum wrote:
On Thu, 21 Aug 2008 10:47:04 Oleg
Michael McCallum wrote:
On Thu, 21 Aug 2008 10:47:04 Oleg Gusakov wrote:
I'm confused... you are distriguishing between local and remote repositories
when you've just abstracted the concept into a virtual reader... why?
This is more implementation details, for user it's hidden by
