You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2007/05/15 22:05:21 UTC

[jira] Updated: (MRELEASE-231) Rewriting scm urls when a tagBase parameter is present.

     [ http://jira.codehaus.org/browse/MRELEASE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier updated MRELEASE-231:
-------------------------------

    Attachment: maven-release-manager.patch

Patch file contains changes to determine the relative url between the trunk and the tag.  This relative url is then used for determining what the tag scm.url and scm.connection should be.
The patch also includes a new unit test to verify the new functionality.

> Rewriting scm urls when a tagBase parameter is present.
> -------------------------------------------------------
>
>                 Key: MRELEASE-231
>                 URL: http://jira.codehaus.org/browse/MRELEASE-231
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>          Components: scm
>    Affects Versions: 2.0-beta-5
>            Reporter: Paul Gier
>         Attachments: maven-release-manager.patch
>
>
> For example, I have a simple pom like this:
> {quote}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>org.jboss.maven.test</groupId>
>   <artifactId>maven-build-test-module1</artifactId>
>   <version>1.0-SNAPSHOT</version>
>   <name>Test Project</name>
>   <description>A project to test the release and packaging features of maven</description>
>   <scm>
>     <connection>scm:svn:http://anonsvn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk/</connection>
>     <developerConnection>scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk/</developerConnection>
>     <url>http://fisheye.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/trunk</url>
>   </scm>
>   <build>
>     <plugins>
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>        
>         <artifactId>maven-release-plugin</artifactId>
>         <version>2.0-beta-5</version>          
>         <configuration>
>           <tagBase>https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags</tagBase>
>         </configuration>
>       </plugin>
>     </plugins>
>   </build>
> </project>
> {quote}
> When I prepare a release, the URLs in the scm configuration are translated to the following:
> {quote}
>   <scm>
>     <connection>scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0</connection>
>     <developerConnection>scm:svn:https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0</developerConnection>
>     <url>https://svn.jboss.org/repos/labs/labs/jbossbuild/maven-build-test/tags/maven-build-test-module1-1.0</url>
>   </scm>
> {quote}
> The developer connection is correct because it is based off the tagBase, but the connection and url in this case are now pointing to the wrong place.
> Maybe there should be separate release plugin parameters similar to tagBase, but used for setting the tag urls for scm.connection and scm.url.

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