[
https://issues.apache.org/jira/browse/SCM-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961810#comment-17961810
]
ASF GitHub Bot commented on SCM-498:
------------------------------------
jira-importer opened a new issue, #711:
URL: https://github.com/apache/maven-scm/issues/711
**[Mark
Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)**
opened
**[SCM-498](https://issues.apache.org/jira/browse/SCM-498?redirect=false)** and
commented
Currently we use 'origin' and the configuration behind it in .git/config
[remotes] when e.g. pushing to the upstream repo.
This causes problems if a -Dusername or -Dpassword is supplied, because
'origin' still doesn't reflect those settings.
solution:
we should use the dynamically created URL (with applied username and
password) for each and every location reference in the maven-scm-providers-git.
While doing this, we should also consider to maintain 2 separate URLs for
fetching and pushing.
---
**Affects:** 1.2
**Issue Links:**
- [SCM-516](https://issues.apache.org/jira/browse/SCM-516) git provider
doesn't respect username in settings.xml
(_**"is duplicated by"**_)
> git providers should use the fetch and push URLs instead of 'origin'
> ---------------------------------------------------------------------
>
> Key: SCM-498
> URL: https://issues.apache.org/jira/browse/SCM-498
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.2
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Major
> Fix For: 1.3
>
>
> Currently we use 'origin' and the configuration behind it in .git/config
> [remotes] when e.g. pushing to the upstream repo.
> This causes problems if a -Dusername or -Dpassword is supplied, because
> 'origin' still doesn't reflect those settings.
> solution:
> we should use the dynamically created URL (with applied username and
> password) for each and every location reference in the
> maven-scm-providers-git.
> While doing this, we should also consider to maintain 2 separate URLs for
> fetching and pushing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
