Yes. The intent was never to lock everyone in place indefinitely. Although I like the appeal of forcing people to choose to upgrade the plugin versions and start managing them, this isn't what the users have asked for nor expect.
-----Original Message----- From: Christian Edward Gruber [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 09, 2008 9:15 AM To: Maven Developers List Subject: Re: plugin versions in super POM and future releases So just to clarify (with pretend numbers), would this sort of scenario be fair: maven-2.0.9 includes: maven-install-plugin-1.9, maven-test-plugin-2.2 maven-compile-plugin-2.7 but maven-2.0.10 includes: maven-install-plugin-1.9, maven-test-plugin-2.3 maven-compile-plugin-2.8 So then would any two executions of 2.0.9 in its default configuration would always use 1.9 of install and 2.2 of test, etc.? And would it be fair to say that plugin versions might change between maven releases (2.0.x->2.0.x+1 or 2.x->2.x+1), but would not bump until the next maven version? If that logic is true, then I consider the problem mostly solved, and am exceedingly excited about it. Christian. On 9-Apr-08, at 08:55 , Brian E. Fox wrote: > I previously put forth a set of guidelines when we voted on doing this > initially. Essentially we would update the plugins only to non alpha > or > beta versions and versions of plugins that had been released longer > than > a month unless there was a good reason to do otherwise. I don't see > any > benefit in forever locking the plugins to where they are now. For the > plugins that were locked at alphas/betas (like assembly), these should > be upgraded with caution until it reaches a full release version and > then the usual rules apply. > > --------------------------------------------------------------------- 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]
