You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "David C. Hicks" <dh...@allureglobal.com> on 2009/08/27 00:50:52 UTC
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Help with batch-mode release?
Posted by Jörg Schaible <jo...@gmx.de>.
David C. Hicks wrote at Donnerstag, 27. August 2009 16:15:
> Found the problem. Apparently, version 2.0-beta-7 of the release plugin
> is buggy in this area.
Ah, well, no. This functionality was simply not yet implemented ...
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Help with batch-mode release?
Posted by "David C. Hicks" <dh...@i-hicks.org>.
Found the problem. Apparently, version 2.0-beta-7 of the release plugin
is buggy in this area. Upgrading to 2.0-beta-9 appears to fix things.
I'll know in a while if all is well.
Thanks for all the suggestions and input. I should have checked on the
plugin version earlier - just didn't think about it. (forest and trees)
Dave
On 08/27/2009 09:45 AM, Arnaud X Dostes wrote:
> 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.
>
>>>> yes, it reuses the same version for submodules
>>>>
>
> I'm trying to move to a different version than that
> which would be calculated by the mojo, though
>
>>>> I believe, although I have not checked, that not using the batch-mode will cause you to get prompted
>>>>
>
> 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.
>
>>>> for having it done before, I feel your pain, be very careful as once you've entered the version for each module, you'll be prompted for the current version, I've often copy-pasted once too many causing me to start again from scratch, so you want to go slowly
>>>>
>
> Good luck
>
>
> Arnaud DOSTES
>
> -----Original Message-----
> From: David C. Hicks [mailto:dhicks@i-hicks.org]
> Sent: Thursday, August 27, 2009 3:41 PM
> To: Maven Users List
> Subject: Re: Help with batch-mode release?
>
> 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:dhicks@allureglobal.com]
>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: Help with batch-mode release?
Posted by Arnaud X Dostes <ar...@jpmorgan.com>.
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.
>>> yes, it reuses the same version for submodules
I'm trying to move to a different version than that
which would be calculated by the mojo, though
>>> I believe, although I have not checked, that not using the batch-mode will cause you to get prompted
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.
>>> for having it done before, I feel your pain, be very careful as once you've entered the version for each module, you'll be prompted for the current version, I've often copy-pasted once too many causing me to start again from scratch, so you want to go slowly
Good luck
Arnaud DOSTES
-----Original Message-----
From: David C. Hicks [mailto:dhicks@i-hicks.org]
Sent: Thursday, August 27, 2009 3:41 PM
To: Maven Users List
Subject: Re: Help with batch-mode release?
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:dhicks@allureglobal.com]
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Help with batch-mode release?
Posted by "David C. Hicks" <dh...@i-hicks.org>.
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:dhicks@allureglobal.com]
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Help with batch-mode release?
Posted by Arnaud X Dostes <ar...@jpmorgan.com>.
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:dhicks@allureglobal.com]
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org