Tried autoVersionSubmodules last night. It didn't appear to work, but my guess is that it only keeps you from being asked what version to label each submodule. I'm trying to move to a different version than that which would be calculated by the mojo, though. My guess is that I'm going to have to specify it for each submodule, either on the command line or in a properties file. That's this morning's task.

On 08/27/2009 09:05 AM, Arnaud X Dostes wrote:
You should check out continuum (http://continuum.apache.org/), it will take 
care of the 'automated release process' (don't know about Hudson). All you need 
is to click a button, works well.

I wouldn't recommend using the --batch-mode attribute, you do want to get 
prompted for messages.

Try adding -DautoVersionSubmodules=true, it changed my life when I found this 
option : http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html







-----Original Message-----
From: David C. Hicks [mailto:[email protected]]
Sent: Thursday, August 27, 2009 12:51 AM
To: Maven Users
Subject: Help with batch-mode release?

I'm trying to set up a script to handle an automated release process.
I'm using the "releaseVersion" and "developmentVersion" properties to
give me some flexibility with respect to the assigned versions.
However, they don't seem to be sticking.

For instance, my current version is 0.9.27-SNAPSHOT.  I do a
release:prepare using the command:

     mvn --batch-mode release:prepare -DreleaseVersion=1.0.0.26
     -DdevelopmentVersion=1.0.0.27-SNAPSHOT

The prepare builds a tag of 0.9.27 and sets the development version to
0.9.28-SNAPSHOT.

This is a multi-module project.  Is that what's causing this?  Do I
really have to specify the versions for each module?
Thanks,
Dave


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

This email is confidential and subject to important disclaimers and
conditions including on offers for the purchase or sale of
securities, accuracy and completeness of information, viruses,
confidentiality, legal privilege, and legal entity disclaimers,
available at http://www.jpmorgan.com/pages/disclosures/email.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to