Thanks all, we know where to go from here! On Tue, May 4, 2010 at 6:03 PM, Jesse Farinacci <jie...@gmail.com> wrote:
> Hi Ravi, > > On Tue, May 4, 2010 at 7:01 PM, Ravi Luthra <cod...@gmail.com> wrote: > > > > I've heard that locking down the plugin version is a bad practice mostly > > because of major versions of Maven being released. Is this really a bad > > practice? > > Not only is it a best practice, but there is support for you to ensure > you've done your job well[1] as well as locate new versions of plugins > for you to upgrade onto. > > [1] > http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html > [2] > http://mojo.codehaus.org/versions-maven-plugin/display-plugin-updates-mojo.html > > > What consequences would we face if we locked down our versions and > upgraded > > them on our own, rather than allowing Maven to choose for us? > > The only consequence would be that you'd not pick up any critical > plugin updates due to bad plugins, but I'm not very convinced by this. > Usually monitoring for [ANN] on maven-users is sufficient to keep > abreast of changes. > > -Jesse > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
