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.
-----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 11:54 PM To: Maven Developers List Subject: plugin versions in super POM and future releases Hi, I was wondering if anyone had opinions about what happens in 2.0.10, 2.1, etc with the versions of plugins that are now specified in the super POM. My gut feeling is that we should not upgrade these without a change to the modelVersion - the POM should be the sole reference for build behaviour and while I accept that changing the version of Maven can bring some behavioural differences this would be the most significant. On the other hand, we wouldn't want to perpetuate forever bugs that might be in the plugins (especially those that are a bit newer and labelled alpha/beta). I think our default stance from here on should be to make no modifications to the super POM without bumping the modelVersion, but reserve the right to make exceptions if the case arises. How do others feel about this? Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ --------------------------------------------------------------------- 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]
