Re: Committing non-POM files during release:prepare?
I'm fairly certain the answer to the question below is no, but I'm wondering if anyone can definitively say either way. Thanks. On Mon, Jan 9, 2012 at 3:02 PM, Andrew Todd andrew.todd...@gmail.com wrote: Maven 2.2, release plugin. During the preparationGoals, I'm modifying a .properties file that references the Maven project version. When the POM files get committed to Subversion after the preparationGoals have completed, I need this .properties file to get committed as well. Otherwise the release:perform step will fail. Is this possible? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Committing non-POM files during release:prepare?
in http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#completionGoals invoke scm:add Though I am pretty sure all unmodified files which are already in SCM get committed by default On 17 January 2012 14:47, Andrew Todd andrew.todd...@gmail.com wrote: I'm fairly certain the answer to the question below is no, but I'm wondering if anyone can definitively say either way. Thanks. On Mon, Jan 9, 2012 at 3:02 PM, Andrew Todd andrew.todd...@gmail.com wrote: Maven 2.2, release plugin. During the preparationGoals, I'm modifying a .properties file that references the Maven project version. When the POM files get committed to Subversion after the preparationGoals have completed, I need this .properties file to get committed as well. Otherwise the release:perform step will fail. Is this possible? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Committing non-POM files during release:prepare?
Thanks, I somehow missed completionGoals before. However, it doesn't really seem to do what's necessary. Looking at my build log, I can see that the source code is being tagged and committed before completionGoals runs. Not to mention that I'm not sure scm:add is the right command, since my .properties file already exists in the repository. Looking at scm:checkin. On Tue, Jan 17, 2012 at 9:55 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: in http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#completionGoals invoke scm:add Though I am pretty sure all unmodified files which are already in SCM get committed by default On 17 January 2012 14:47, Andrew Todd andrew.todd...@gmail.com wrote: I'm fairly certain the answer to the question below is no, but I'm wondering if anyone can definitively say either way. Thanks. On Mon, Jan 9, 2012 at 3:02 PM, Andrew Todd andrew.todd...@gmail.com wrote: Maven 2.2, release plugin. During the preparationGoals, I'm modifying a .properties file that references the Maven project version. When the POM files get committed to Subversion after the preparationGoals have completed, I need this .properties file to get committed as well. Otherwise the release:perform step will fail. Is this possible? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Committing non-POM files during release:prepare?
sorry yeah, completion goals is for after starting the next version. you can do the same trick in preparation goals though - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 17 Jan 2012 18:36, Andrew Todd andrew.todd...@gmail.com wrote: Thanks, I somehow missed completionGoals before. However, it doesn't really seem to do what's necessary. Looking at my build log, I can see that the source code is being tagged and committed before completionGoals runs. Not to mention that I'm not sure scm:add is the right command, since my .properties file already exists in the repository. Looking at scm:checkin. On Tue, Jan 17, 2012 at 9:55 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: in http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#completionGoals invoke scm:add Though I am pretty sure all unmodified files which are already in SCM get committed by default On 17 January 2012 14:47, Andrew Todd andrew.todd...@gmail.com wrote: I'm fairly certain the answer to the question below is no, but I'm wondering if anyone can definitively say either way. Thanks. On Mon, Jan 9, 2012 at 3:02 PM, Andrew Todd andrew.todd...@gmail.com wrote: Maven 2.2, release plugin. During the preparationGoals, I'm modifying a .properties file that references the Maven project version. When the POM files get committed to Subversion after the preparationGoals have completed, I need this .properties file to get committed as well. Otherwise the release:perform step will fail. Is this possible? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org