RE: chaining release:prepare release:perform for multi-module [I]

2013-07-23 Thread Martin Gainty
release:perform for multi-module [I] From: nathan.co...@db.com Date: Thu, 18 Jul 2013 16:23:17 +0100 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

Re: chaining release:prepare release:perform for multi-module [I]

2013-07-19 Thread Nathan Coast
to place the credentials in the settings.xml in order for the build to succeed. Any suggestions? Regards, Nathan From: Ziga Gregoric ziga.grego...@gmail.com To: Maven Users List users@maven.apache.org, Date: 18/07/2013 16:43 Subject: Re: chaining release:prepare release:perform for multi-module

Re: chaining release:prepare release:perform for multi-module [I]

2013-07-19 Thread Ziga Gregoric
users@maven.apache.org, Date: 18/07/2013 16:43 Subject: Re: chaining release:prepare release:perform for multi-module [I] Nathan, 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

chaining release:prepare release:perform for multi-module [I]

2013-07-18 Thread Nathan Coast
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

Re: chaining release:prepare release:perform for multi-module [I]

2013-07-18 Thread Ziga Gregoric
Nathan, 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