maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcin Kuthan (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRELEASE-335) release:branch commits changes to tags/ directory
Date Thu, 23 Dec 2010 09:56:58 GMT

    [ http://jira.codehaus.org/browse/MRELEASE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249540#action_249540
] 

Marcin Kuthan commented on MRELEASE-335:
----------------------------------------

Hi Frederic

I just check again my repository and <version> and <scm> were updated in the branch
pom. You can find an example there:
http://code.google.com/p/m4enterprise/source/browse/branches/1.0.x/pom.xml?r=777

The only disadvantage is that I have to execute release:branch in interactive mode. I didn't
find a solution how to pass the next branch version as a property.

> release:branch commits changes to tags/ directory
> -------------------------------------------------
>
>                 Key: MRELEASE-335
>                 URL: http://jira.codehaus.org/browse/MRELEASE-335
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: scm
>    Affects Versions: 2.0-beta-7
>            Reporter: Alex B
>
> It should be possible to create a branch from a tag using the release plugin without
comitting changes to the tags/ directory in subversion.
> If this cannot be automated, then perhaps it should be possible to set the versions and
scm urls etc after making the copy from the tag to the branch manually....

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message