Even though a plug-in update should be checked, tested and harmless, lots of corporations have a lot of processes in place regarding build reproducability. Doing a build with the updated v1.1 maven-foo-plugin could cause the build to look ever so slightly different than the build previously done with the orignial v1.0. This could cause red flags to go flying. I'd think an easy flag for disabling automatic plug-in updating is a must.
On 5/19/05, Brett Porter <[EMAIL PROTECTED]> wrote: > A couple of ways presently: > > - use -o on the command line (it can be in MAVEN_OPTS), but this > disables all downloads > - ad a pluginRepository to your project (or one you inherit from) with > id = central and <snapshotPolicy>never</snapshotPolicy> > - explicitly list all plugins you use in pom.xml with their versions. > > We intend to improve this in the next release: > http://jira.codehaus.org/browse/MNG-379 > > Note that plugin updates should only be checked, and published after > sufficient testing so there should be no harm in leaving it enabled at > the moment. > > Regards, > Brett > > On 5/19/05, Malcolm Wong Ho <[EMAIL PROTECTED]> wrote: > > > > How do i disable the Automatic Maven Plugin Updates in Maven2 ? > > > > -- > > Malcolm Wong Ho > > > > May you live in uninteresting times. -- Chinese proverb > > > > --------------------------------------------------------------------- > > 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] > > -- Jamie Bisotti Software Engineer Lexmark International, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
