-1. if I recall the discussion about plugin versions in super pom correctly, the solution was accepted not as a way to have 100% reprodicible build, but have reproducible builds with one version of maven for a duration longer than a few weeks (exagerating here a bit). So it's basically just a way to improve the first impression for new users and reduce the learning cur[vs]e.The correct bullet-proof solution remains to have the versions declared in your pom I think.
Milos On Wed, Apr 9, 2008 at 7:43 AM, nicolas de loof <[EMAIL PROTECTED]> wrote: > Putting (core) plugin versions in the super POM is not a full fix for > projects to be reproductible. Users can still use other non-core > plugins without a version set. > > Based on this, I'm +0 to let the superPOM plugins as is as I'd prefer a rule > to have NO plugin with version unset. > > Could we move the pluginVersion enforcer rule to the maven core as a 2.0.10 > / 2.1 feature ? > > > 2008/4/9, Brett Porter <[EMAIL PROTECTED]>: > > > > > > 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]
