maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony O. (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRELEASE-642) prepare tags the wrong source
Date Fri, 04 Feb 2011 15:26:22 GMT

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

Anthony O. commented on MRELEASE-642:
-------------------------------------

Here is a workaround : set {{remoteTagging}} to {{false}}
{noformat}
        <plugin>
            <artifactId>maven-release-plugin</artifactId>
            <version>2.1</version>
            <configuration>
                <tagBase>http://svn.mycompany.com/svn/project/releases</tagBase>
                <generateReleasePoms>false</generateReleasePoms>
                <autoVersionSubmodules>true</autoVersionSubmodules>
                <remoteTagging>false</remoteTagging>
            </configuration>
        </plugin>
{noformat}

Here is the output of {{mvn release:prepare-with-pom}} :
{noformat}
[INFO] Executing: /bin/sh -c cd /home/user/project/dev/project-parent && svn --non-interactive
commit --file /tmp/maven-scm-1771596856.commit --targets /tmp/maven-scm-705724546525349400-targets
[INFO] Working directory: /home/user/project/dev/project-parent
[INFO] Tagging release with the label project-<release-version>...
[INFO] Executing: /bin/sh -c cd /home/user/project/dev && svn --non-interactive copy
--file /tmp/maven-scm-402885419.commit . http://svn.mycompany.com/svn/project/releases/project-<release-version>
[INFO] Working directory: /home/user/project/dev
{noformat}

> prepare tags the wrong source
> -----------------------------
>
>                 Key: MRELEASE-642
>                 URL: http://jira.codehaus.org/browse/MRELEASE-642
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.1
>            Reporter: Anthony O.
>
> The use case is mostly defined [here|http://stackoverflow.com/questions/4856364/tagging-sub-trunk-directory-when-releasing-with-maven-using-svn]
> Here is our svn structure :
> {noformat}
> trunk/
>  +- docs/
>  +- dev/
>      +- project-parent/
>          +- pom.xml
>      +- project-war/
>          +- pom.xml
> releases/
> {noformat}
> When preparing the release ({{mvn release:prepare-with-pom}}), I want to tag {{trunk/dev/}}
into {{releases/project-<release-version>/}}.
> The parent {{pom.xml}} is like this :
> {noformat}
> <build>
>     <plugins>
>         <plugin>
>             <artifactId>maven-release-plugin</artifactId>
>             <version>2.1</version>
>             <configuration>
>                 <tagBase>http://svn.mycompany.com/svn/project/releases</tagBase>
>                 <generateReleasePoms>false</generateReleasePoms>
>                 <autoVersionSubmodules>true</autoVersionSubmodules>
>             </configuration>
>         </plugin>
>     </plugins>
> </build>
> <scm>
>     <connection>scm:svn:http://svn.mycompany.com/svn/project/trunk/dev</connection>
>     <developerConnection>scm:svn:http://svn.mycompany.com/svn/project/trunk/dev</developerConnection>
>     <url>scm:svn:http://svn.mycompany.com/svn/project/trunk/dev</url>
> </scm>
> {noformat}
> My working copy {{/home/user/project}} is checked out from {{http://svn.mycompany.com/svn/project/trunk/}}.
> When doing {{mvn release:prepare-with-pom -DdryRun=true}}, it says me that :
> {noformat}
> [INFO] Full run would be tagging working copy /home/user/project/dev with label: 'project-<release-version>'
> {noformat}
> But, when removing {{-DdryRun=true}}, here is what the plugin does :
> {noformat}
> [INFO] Executing: /bin/sh -c cd /home/user/project/dev/project-parent && svn
--non-interactive commit --file /tmp/maven-scm-1922580928.commit --targets /tmp/maven-scm-8496598021737984450-targets
> [INFO] Working directory: /home/user/project/dev/project-parent
> [INFO] Tagging release with the label project-<release-version>...
> [INFO] Executing: /bin/sh -c cd /home/user/project/dev && svn --non-interactive
copy --file /tmp/maven-scm-982655546.commit --revision <revision> http://svn.mycompany.com/svn/project/trunk
http://svn.mycompany.com/svn/project/releases/project-<release-version>
> [INFO] Working directory: /home/user/project/dev
> {noformat}
> So, with {{dryRun}} we think that it is {{trunk/dev}} which will be tagged, and when
doing a real prepare, it is finally {{trunk/}} which is tagged, and *this is not espected*.

-- 
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