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 AM, 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 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 g:a:RELEASE, so I merge these two in Mercury.
Please comment in
http://docs.codehaus.org/display/MAVEN/Mercury+Repository+Abstraction#MercuryRepositoryAbstraction-ArtifactVersionsspecialtreatment
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
You are never dedicated to something you have complete confidence in.
No one is fanatically shouting that the sun is going to rise tomorrow.
They know it is going to rise tomorrow. When people are fanatically
dedicated to political or religious faiths or any other kind of
dogmas or goals, it's always because these dogmas or
goals are in doubt.
-- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
