I had already gone through that page.  It was just not real clear to me
if one must really specify the version for each module in a multi-module
batch build.  At your suggestion, I added autoVersionSubmodules to my
command line, but that didn't have any noticeable effect on the result. 
The new command line looks like this:

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

I guess I'll have to try specifying the version for each module and see
if that helps.

Thanks for the thoughts.
Dave


Kalle Korhonen wrote:
> Read the part about multi-module non-interactive releases:
> http://maven.apache.org/plugins/maven-release-plugin/examples/non-interactive-release.html.
> I have not tried overriding versions, but I do most of my multi-module
> release in batch mode. I always specify autoVersionSubmodules=true (in
> the pom) - that might be one thing you are missing.
>
> Kalle
>
>
> On Wed, Aug 26, 2009 at 4:05 PM, David C. Hicks<[email protected]> wrote:
>   
>> 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]
>>
>>
>>     
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>   

Reply via email to