maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ziga Gregoric <>
Subject Re: chaining release:prepare release:perform for multi-module [I]
Date Thu, 18 Jul 2013 15:42:38 GMT

Strategy working for me is to have two jobs, one doing mvn clean
install on every commit and another for release.

The release job would do mvn release:prepare release:perform
--batch-mode on my multi module project's parent pom.

With TeamCity and svn it works great, and the install job gives me a
safety net that trunk is green.


On 18. jul. 2013, at 17:23, Nathan Coast <> wrote:

Classification: For internal use only

Hi all,

I appreciate the "normal" approach to executing a maven release is to
execute release:prepare, followed by release:perform

I am attempting to set up a release job within our build server (TeamCity)
which will atomically create a release.  Assuming successful execution.

mvn release:prepare release:perform

My concern is that this will execute prepare followed by perform upon each
module in the reactor build order.  Where what is needed is for
release:prepare to be executed in full, followed by release perform in

Is there any way to configure this in a single chained command?  Or will I
have to configure multiple build jobs and link the jobs?



This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and delete this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.

Please refer to for
additional EU corporate and regulatory disclosures.

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message