: den 1 september 2006 10:44
To: users@maven.apache.org
Subject: Re: Reproducing maven builds versus auto updating maven.
Lock down all your plugin versions.
plugin
groupId...
artifactId...
version2.0-beta5/version
...
Since I 've done that I experience it as being much much more
I recently gave a quick hands on introductions to Maven (v2) at the
company I'm currently consulting at. The company is now interested in
testing maven out in a project. There are two major and related concerns
I have though with using maven:
1. Maven updates itself at a regular basis.
Lock down all your plugin versions.
plugin
groupId...
artifactId...
version2.0-beta5/version
...
Since I 've done that I experience it as being much much more in control
over the build process. When a new plugin is released, I change the
version and test it locally first before
maven builds versus auto updating maven.
Lock down all your plugin versions.
plugin
groupId...
artifactId...
version2.0-beta5/version
...
Since I 've done that I experience it as being much much more in control
over the build process. When a new plugin is released, I change the
version
Hi,
looking at reproducable builds, I would consider auto updating of
anything as a bug. WDYT?
Bernd
I recently gave a quick hands on introductions to Maven (v2) at the
company I'm currently consulting at. The company is now interested in
testing maven out in a project. There are two major
[mailto:[EMAIL PROTECTED] On Behalf Of Geoffrey De Smet
Sent: den 1 september 2006 10:44
To: users@maven.apache.org
Subject: Re: Reproducing maven builds versus auto updating maven.
Lock down all your plugin versions.
plugin
groupId...
artifactId...
version2.0-beta5/version
...
Since I 've
@maven.apache.org
Subject: Re: Reproducing maven builds versus auto updating maven.
Lock down all your plugin versions.
plugin
groupId...
artifactId...
version2.0-beta5/version
...
Since I 've done that I experience it as being much much more in control
over the build process. When a new