On Sep 11, 2012, at 7:02 PM, "KARR, DAVID" <[email protected]> wrote:
> I noticed a comment in > http://www.dzone.com/links/r/continuous_delivery_using_maven_3.html about not > using the release plugin because it checks in POMs after updating versions, > which isn't suited to a continuous delivery pipeline. Is the release plugin > intended to be run manually, and not part of an automated build? > > The documentation for the plugin doesn't really address this question. The deploy phase is typically used for CI. See http://www.sonatype.com/books/mvnref-book/reference/lifecycle-sect-common-goals.html#lifecycle-sect-deploy-phase. Release is different, it's what you do when you want to update the version numbers and have a concrete reproducible point in the source tree. Most orgs do this manually because of the care that is required, but I've set it up as a pushbutton on CI servers for folks that don't have a lot at stake. They are both supported by plugins with those names, but they are very distinct in the project lifecycle. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
