Hi, As a heavy Maven **user**, what would be best for us is having some plugin (could be the enforcer, or another) automatically generate this configuration for us into the POM. Something along the lines of:
mvn enforcer:lock-plugins This command will find the most appropriate version of relevant plugins and modify my POM(s) to explicitly specify them. Later on, I can either manually modify my POM when I want to upgrade a plugin, or run another command, e.g: mvn enforcer:update-all-plugins or: mvn enforcer:update-plugin -DgroupId=org.apache.maven.plugins-DartifactId=maven-jar-plugin -Dversion=latest/2.9.9.9 Current behavior should remain, if only not to upset the many non-enterprise users which use Maven more "lightly". HTH, Arik. On 9/2/07, Dan Tran <[EMAIL PROTECTED]> wrote: > > B > > Totally agree with Wayne here. > > -D > > On 9/2/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > > > [X] (B) Retain the current behaviour, but make using the enforcer a > > > best practice to do the above, or some other control mechanism such > > > as having the repository manager handle the available plugins > > > > I am thinking about the new user experience and winning more converts. > As such, I think the current behavior is best. Once they get using Maven > more seriously (and in corporate environments that know what they're doing), > I think adding the Enforcer configuration and locking versions down will > come naturally. But *requiring* it seems excessive -- unless we're doing > that ourselves somewhere, with plugin packs or similar, then I feel better > about it. > > > > Wayne > > > > --------------------------------------------------------------------- > > 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] > >