maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleg Gusakov <oleg.subscripti...@gmail.com>
Subject Re: version LATEST merge with RELEASE
Date Thu, 21 Aug 2008 00:19:02 GMT
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 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.
>>
>>     
> Doesn't this just make people lazy and not think about what they are doing... 
> if they want an open range [1,) then let them specify that?
>
> I suppose if you just mapped that at the very beginning down to an open range 
> it probably does not make any difference implementationwise however anyother 
> tool that wants to make sense of the pom needs to understand all the special 
> cases too...
>
>   

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message