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
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
On 5 May 2010 00:01, Ravi Luthra cod...@gmail.com 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
You should lock down plugin versions in your enterprise pom. Whomever told you
otherwise was on crack.
Justin
On May 4, 2010, at 7:01 PM, Ravi Luthra cod...@gmail.com wrote:
At our company we maintain a top-level enterprise pom that all projects
inherit. We're considering adding versions to
It is totally best practice to lock your plugin versions and much more
down. Depending on the usage of your company pom and the content you could
even introduce a company super pom.
Have a look here for what I mean.
http://www.mosabuam.com/2009/10/company-super-pom-a-maven-practice
manfred
At
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
