On 5 May 2010 00:01, Ravi Luthra <[email protected]> wrote: > At our company we maintain a top-level enterprise pom that all projects > inherit. We're considering adding versions to lock down our plugin > versions. > What we are trying to avoid is having our build break because of a > third-party plugin upgrading on us unexpectedly. > > 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? >
You heard wrong. Locking down the plugin versions is best practice > > 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? > > Thanks, > Ravi >
