I think that by setting the versions in the superpom, we would already have eliminated the issue you fear...however going by memory, 2.0.8 came out before 2.4 and if that's the case, then surely we wouldn't have that version in the pom.
I think it's safe to say that the versions idea will go forward and I'll make the changes as soon as I grab some time this week. I have some loose guidelines in mind that probably need some definition. I think that the thing we all fear most is a plugin version tied to maven that breaks lots of people's builds and requiring a Maven update simply to get people up to the next plugin rev. To avoid that, I think we need some time limit and judgement calls on the versions that get into the superpom. We definitely don't want to automatically bump the superpom version simply because a plugin was released. I would say that the initial hurdle for a plugin to be included is being in the wild for 1 month (possibly longer for major updates like surefire 2.4). The whole point of this change is stability and thus we should err on the conservative side when choosing these versions. Those who want/need the bleeding edge can change their poms (something I will continue to advocate regardless). Ultimately there will be no hard rules and we'll have to pay very close attention to all versions being changed in each maven release. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Benedict Sent: Tuesday, February 12, 2008 1:23 PM To: Maven Developers List Subject: Maven and preset plugin versions I've been watching the discussions about introducing a fix set of plugin versions per Maven version. I see benefit and drawback to each side of the argument. Here is another proposal which is dear to my pain :-) Provide the minimal compatible version of each plugin (of group org.apache.maven.plugins) in the super pom. For instance, when I upgraded to Maven 2.0.8, it would have been nice (stupendous!) to automatically be bumped to surefire 2.4 because the two truly needed each other in integration testing. I imagine there are other cases when plugins have dependencies on other parts of the Maven core, but I could be wrong. The desire is for children pom to provide the "better" versions if necessary, but Maven should at least provide the minimum versions. Paul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
