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

Iwao AVE! commented on MRELEASE-718:
------------------------------------

Dennis,

I have tried 'mvn scm:validate' with the invalid developerConnection value, but 
it says the connection string is valid.

[INFO] connectionUrl scm connection string is valid.
[INFO] project.scm.connection scm connection string is valid.
[INFO] project.scm.developerConnection scm connection string is valid.

Anyway, thank you very much for your time!

Regards,
Iwao

> SCM URL specified for the developerConnection is mistranslated
> --------------------------------------------------------------
>
>                 Key: MRELEASE-718
>                 URL: https://jira.codehaus.org/browse/MRELEASE-718
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.1
>         Environment: $ mvn --version
> Apache Maven 3.0.3 (r1075438; 2011-03-01 02:31:09+0900)
> Maven home: /usr/share/maven
> Java version: 1.6.0_26, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: ja_JP, platform encoding: SJIS
> OS name: "mac os x", version: "10.6.8", arch: "x86_64", family: "mac"
>            Reporter: Iwao AVE!
>
> With the following scm entry, release:parepare fails with the error message 
> below.
> The repository URL in the log message does not match with the scm URL 
> specified in the developerConnection (':' after 'jp' is missing).
> <scm>
>   <url>http://git.sourceforge.jp/view?p=myproj/mymodule.git</url>
>   
> <connection>scm:git:git://git.sourceforge.jp/gitroot/myproj/mymodule.git</connection>
>   
> <developerConnection>scm:git:usern...@git.sourceforge.jp:/gitroot/myproj/mymoduje.git</developerConnection>
> </scm>
> [INFO] Checking in modified POMs...
> [INFO] Executing: /bin/sh -c cd /Users/me/wc/mymodule && git add -- pom.xml
> [INFO] Working directory: /Users/me/wc/mymodule
> [INFO] Executing: /bin/sh -c cd /Users/me/wc/mymodule && git status
> [INFO] Working directory: /Users/me/wc/mymodule
> [INFO] Executing: /bin/sh -c cd /Users/me/wc/mymodule && git commit --verbose 
> -F 
> /var/folders/As/AsF6MEp1HPe8ABO0cOmqtE+++TI/-Tmp-/maven-scm-1655418274.commit 
> pom.xml
> [INFO] Working directory: /Users/me/wc/mymodule
> [INFO] Executing: /bin/sh -c cd /Users/me/wc/mymodule && git symbolic-ref HEAD
> [INFO] Working directory: /Users/me/wc/mymodule
> [INFO] Executing: /bin/sh -c cd /Users/me/wc/mymodule && git push 
> usern...@git.sourceforge.jp/gitroot/myproj/mymodule.git master:master
> [INFO] Working directory: /Users/me/wc/mymodule
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Total time: 40.500s
> [INFO] Finished at: Thu Nov 17 03:32:26 JST 2011
> [INFO] Final Memory: 5M/81M
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli) on 
> project mymodule: Unable to commit files
> [ERROR] Provider message:
> [ERROR] The git-push command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'usern...@git.sourceforge.jp/gitroot/myproj/mymodule.git' does 
> not appear to be a git repository
> [ERROR] fatal: The remote end hung up unexpectedly
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to