[
https://jira.codehaus.org/browse/SCM-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320608#comment-320608
]
Christophe Furmaniak commented on SCM-707:
------------------------------------------
I did not confuse maven and jenkins logging. The problem I noticed regarding
the fact that the password is not "stared" when it contains special chars
happens in pure maven command line.
> Maven SCM should encode username and password in URL
> ----------------------------------------------------
>
> Key: SCM-707
> URL: https://jira.codehaus.org/browse/SCM-707
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git, maven-scm-provider-mercurial
> (hg), maven-scm-provider-svn
> Affects Versions: 1.8
> Reporter: Sebastien Deleuze
> Fix For: 1.9
>
>
> When using SCM over http (tested in my case with Git), Maven SCM should
> encode username and password before using them with URL.
> In order to reproduce, try to create a release with Maven Release and a user
> with a password containing @ character, it will fail.
> Please find bellow cmd output :
> [INFO] Executing: /bin/sh -c cd /DATA/jenkins/workspace/path && git push
> http://username:*********@git.forge/git/project/ master:master
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.4:prepare (default-cli)
> on project project: Unable to commit files
> Provider message:
> The git-push command failed.
> Command output:
> error: Couldn't resolve host '@*******@git.forge' while accessing
> http://username:*********@git.forge/git/project/info/refs
> fatal: HTTP request failed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
