[ 
https://jira.codehaus.org/browse/MRELEASE-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343752#comment-343752
 ] 

Kelly Davis commented on MRELEASE-767:
--------------------------------------

I just tried 2.5 on one of my projects and unfortunately it is does not appear 
to be fixed. It looks like the scm url is still getting mangled. This should be 
re-opened

> releasing flat multi-module projects using git
> ----------------------------------------------
>
>                 Key: MRELEASE-767
>                 URL: https://jira.codehaus.org/browse/MRELEASE-767
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.3.1
>         Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800)
> Maven home: /usr/share/maven
> Java version: 1.6.0_31, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.7.4", arch: "x86_64", family: "mac"
>            Reporter: Jeremy Norris
>            Assignee: Mark Struberg
>             Fix For: 2.5
>
>
> When releasing a project as follows:
> ./parent/pom.xml
> ./module-a/pom.xml
> ./module-b/pom.xml
> From the parent directory, with an scm config in the parent pom.xml (only) as 
> follows:
> <scm>
>   <connection>scm:git:ssh://github.com/repox.git</connection>
>   
> <developerConnection>scm:git:ssh://github.com/repox.git</developerConnection>
>   <tag>master</tag>
>   <url>https://github.com/view/repox.git</url>
> </scm>
> In org/apache/maven/shared/release/util/ReleaseUtils.java:182 it does this 
> indiscriminately:
> url = realignScmUrl( parentLevels, url );
> This will trim the repo url from 'ssh://github.com/repox.git' -> 
> 'ssh://github.com', which will cause a failure when pushing the tag.
> This type of realignment is not appropriate when using a git scm type.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to