We have a problem with how our build process uses automated checkouts with
the maven release plugin. First a little background:
o We "release" our project each time we perform a nightly build. This
means each build gets a unique version number, where the last digit is a
build number.
o We use AnthillOS to run our build process. If any files have changed
since the last checkout, AnthillOS will check out the project, then invoke
Maven 2 to perform the actual build and release, which we perform using the
release plugin.
Since the release plugin checks in a new verion of the POM during the
release, the next evening a new checkout happens even if the developer has
not checked in any changes. We end up getting a lot of builds where the only
difference is the version number in the POM.
Has anyone faced this situation or have a suggestion on how I might address
it? We're just starting to migrate our Maven 1 builds to Maven 2, so I'm
fine with moving to a new build manager if it can handle this situation.
Thanks for any leads.
Jeff
--
View this message in context:
http://old.nabble.com/Release-plug-in-fools-automated-checkout-process-tp27347404p27347404.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
