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
. 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.
In theory, any plugin target can be executed as part of an automated build, the
release plugin is no different.
Regards,
Graham
--
smime.p7s
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
-- but that's my job as an SCM engineer :)
Thanks,
Roy
-Original Message-
From: KARR, DAVID [mailto:dk0...@att.com]
Sent: Tuesday, September 11, 2012 11:02 AM
To: Maven Users List
Subject: Is the release plugin intended to be run manually?
I noticed a comment in
http://www.dzone.com/links/r
think is as easy as it may at first sound.
-Original Message-
From: Lyons, Roy [mailto:roy.ly...@cmegroup.com]
Sent: Tuesday, September 11, 2012 12:43 PM
To: Maven Users List
Subject: RE: Is the release plugin intended to be run manually?
My recommendation is to keep your release
I noticed a comment in ... 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 plugin can be used in an automated
Every time that 'continuous delivery' shows up on this mailing list,
we end up with 10,000 lines of opinionated email about this
extraordinarily controversial topic.
I respectfully plead with all of you to use this mailing list for
practical, answerable, questions about the behavior of Maven, and
What will happen to maven if we moderate discussions touching continuous
delivery aggressively?
Those who do want to use CD, which tools will they use? Where can they
learn how to use maven for CD?
How can maven developers learn how maven could evolve to facilitate maven
usage in CD setups?
I have used maven for CD on some projects... But I find CD to be less
useful than a simple release often approach.
The key take home of CD for me is that you always should be able to release
the master branch. That no long lived branches should exist is secondary.
Actually pushing releases every
