You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Frederic Camblor <fc...@gmail.com> on 2010/11/02 17:59:59 UTC
Re: Maven release:branch commiting things on tags
Really nobody has encountered the problem ?
Should I fill an issue then ?
Frederic
On Fri, Oct 15, 2010 at 7:08 PM, Frederic Camblor <fc...@gmail.com>wrote:
> Hi maven users !
>
> I learned something some days ago, about maven-release-plugin about its
> branch goal.
>
> Currently, I execute following command line :
>
> mvn --batch-mode org.apache.maven.plugins:maven-release-plugin:2.0:branch -DautoVersionSubmodules=true -DtagBase=tags/ -Dtag=1.0.0 -DupdateBranchVersions=true -DreleaseVersion=2.0.0 -DbranchBase=branches/ -DbranchName=2.0.0
>
> My goal, here, is to create a new branch called "2.0.0" from the 1.0.0 tag.
>
> It works great but I found something crappy : some commit were made on the
> 1.0.0 tag hierarchy.
> That is to say, the plugin is acting this way :
> - Checkout tag ${tagBase}${tag} in working directory
> - Modify pom to ${releaseVersion}-SNAPSHOT & scm
> - Commit pom (on tag 1.0.0 !!!)
> --------- If something is going bad during the next two lines, your tag
> hierarchy will be altered
> - SVN Copy ${tagBase}${tag}/ hierarchy to ${branchBase}${branchName}/
> hierarchy
> - Re-Modify pom in working directory to ${tag}
> - Re-Commit pom on tag 1.0.0
>
> I would think it would act this way :
> - SVN Copy ${tagBase}${tag}/ hierarchy to ${branchBase}${branchName}/
> hierarchy
> - Checkout ${branchBase}${branchName}/ in working directory
> - Modify pom to ${releaseVersion}-SNAPSHOT
> - Commit pom (on branch !) & scm
>
> Would it be some reason why the first strategy is applied ?
> Am I badly using release:branch goal ?
>
> Thanks in advance for your precisions.
> Frédéric
>
Re: Maven release:branch commiting things on tags
Posted by Wendy Smoak <ws...@gmail.com>.
On Tue, Nov 9, 2010 at 12:30 PM, Frederic Camblor <fc...@gmail.com> wrote:
> -DupdateWorkingCopyVersion=false doesn't solve the problem.
>
> Just filed a JIRA : http://jira.codehaus.org/browse/MRELEASE-612
I linked it to http://jira.codehaus.org/browse/MRELEASE-335 (and
closed it as a duplicate).
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven release:branch commiting things on tags
Posted by Frederic Camblor <fc...@gmail.com>.
-DupdateWorkingCopyVersion=false doesn't solve the problem.
Just filed a JIRA : http://jira.codehaus.org/browse/MRELEASE-612
On Mon, Nov 8, 2010 at 11:35 PM, Jon Paynter <ki...@gmail.com> wrote:
>
> I ran into simmilar behavior when trying to persuade the plugin to make me
> a
> new branch. The plugin seems to get very confused when you change the
> default values of updateWorkingCopyVersions or updateBranchVersions.
>
> I did not get a strait answer so i found another solution here:
> http://mojo.codehaus.org/versions-maven-plugin/
>
> Definately file an issue.
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Re-Maven-release-branch-commiting-things-on-tags-tp3247052p3255932.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Maven release:branch commiting things on tags
Posted by Jon Paynter <ki...@gmail.com>.
I ran into simmilar behavior when trying to persuade the plugin to make me a
new branch. The plugin seems to get very confused when you change the
default values of updateWorkingCopyVersions or updateBranchVersions.
I did not get a strait answer so i found another solution here:
http://mojo.codehaus.org/versions-maven-plugin/
Definately file an issue.
--
View this message in context: http://maven.40175.n5.nabble.com/Re-Maven-release-branch-commiting-things-on-tags-tp3247052p3255932.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven release:branch commiting things on tags
Posted by Zac Thompson <za...@gmail.com>.
Try with -DupdateWorkingCopyVersions=false ... I don't know if it will
solve your problem but it definitely seems like something you should
include
On Tue, Nov 2, 2010 at 9:59 AM, Frederic Camblor <fc...@gmail.com> wrote:
> Really nobody has encountered the problem ?
>
> Should I fill an issue then ?
>
> Frederic
>
> On Fri, Oct 15, 2010 at 7:08 PM, Frederic Camblor <fc...@gmail.com>wrote:
>
>> Hi maven users !
>>
>> I learned something some days ago, about maven-release-plugin about its
>> branch goal.
>>
>> Currently, I execute following command line :
>>
>> mvn --batch-mode org.apache.maven.plugins:maven-release-plugin:2.0:branch -DautoVersionSubmodules=true -DtagBase=tags/ -Dtag=1.0.0 -DupdateBranchVersions=true -DreleaseVersion=2.0.0 -DbranchBase=branches/ -DbranchName=2.0.0
>>
>> My goal, here, is to create a new branch called "2.0.0" from the 1.0.0 tag.
>>
>> It works great but I found something crappy : some commit were made on the
>> 1.0.0 tag hierarchy.
>> That is to say, the plugin is acting this way :
>> - Checkout tag ${tagBase}${tag} in working directory
>> - Modify pom to ${releaseVersion}-SNAPSHOT & scm
>> - Commit pom (on tag 1.0.0 !!!)
>> --------- If something is going bad during the next two lines, your tag
>> hierarchy will be altered
>> - SVN Copy ${tagBase}${tag}/ hierarchy to ${branchBase}${branchName}/
>> hierarchy
>> - Re-Modify pom in working directory to ${tag}
>> - Re-Commit pom on tag 1.0.0
>>
>> I would think it would act this way :
>> - SVN Copy ${tagBase}${tag}/ hierarchy to ${branchBase}${branchName}/
>> hierarchy
>> - Checkout ${branchBase}${branchName}/ in working directory
>> - Modify pom to ${releaseVersion}-SNAPSHOT
>> - Commit pom (on branch !) & scm
>>
>> Would it be some reason why the first strategy is applied ?
>> Am I badly using release:branch goal ?
>>
>> Thanks in advance for your precisions.
>> Frédéric
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org