[ 
https://issues.apache.org/jira/browse/SCM-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962645#comment-17962645
 ] 

ASF GitHub Bot commented on SCM-707:
------------------------------------

jira-importer commented on issue #914:
URL: https://github.com/apache/maven-scm/issues/914#issuecomment-2964632744

   **[Michaël 
Defretin](https://issues.apache.org/jira/secure/[email protected])**
 commented
   
   Same problem here. I can't change my password given by my admnistrator and 
this password contains @ ...
   




> Maven SCM should encode username and password in URL
> ----------------------------------------------------
>
>                 Key: SCM-707
>                 URL: https://issues.apache.org/jira/browse/SCM-707
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-gitexe, maven-scm-provider-mercurial 
> (hg), maven-scm-provider-svn
>    Affects Versions: 1.8
>            Reporter: Sébastien Deleuze
>            Assignee: Robert Scholte
>            Priority: Major
>             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 was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to