The idea originally was that LATEST might refer to a snapshot release, but that RELEASE was the latest plugin release. Of course, all of this completely ignores any notion of versions that have implications for backward compatibility. In the Maven 2.0.x, all plugin releases are assumed to be minor/point releases of the same major version.
-john On 4/11/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
I never use either to be honest so I'm not actually sure what the difference is. -----Original Message----- From: Barrie Treloar [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 11, 2007 6:44 PM To: Maven Developers List Subject: Re: [vote] Attempt 3: Release maven-assembly-plugin 2.2-beta-1 -> lock down of plugin versions On 4/12/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > I think if we just change the plugin resolution so that it doesn't > assume "RELEASE" if no version is set, it should be pretty easy right? > IE someone can still put RELEASE as a version if they want to, but we > would require something to be set and not just assume it. Or should we > abandon RELEASE all together? Is this because LATEST and RELEASE might not be the same thing? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
