[
https://issues.apache.org/jira/browse/SCM-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962916#comment-17962916
]
ASF GitHub Bot commented on SCM-765:
------------------------------------
jira-importer opened a new issue, #972:
URL: https://github.com/apache/maven-scm/issues/972
**[Bartholdi
Dominik](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=imod)**
opened
**[SCM-765](https://issues.apache.org/jira/browse/SCM-765?redirect=false)** and
commented
When using the jgit provider over http, it allows to define username /
password like this:
```
mvn release:prepare release:perform -Dresume=false -Dusername=myuser
-Dpassword=XXX
```
But the commit will not be done with the given user but with the system user
who started the process, instead the passed user is only used for transport.
Well that might be fine in the first thought, but it will mean in the git
repository it is not recorded who really did make the release.
---
**Affects:** 1.9
> jgit provider commits changes with system user instead of passed username
> -------------------------------------------------------------------------
>
> Key: SCM-765
> URL: https://issues.apache.org/jira/browse/SCM-765
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.9
> Reporter: Bartholdi Dominik
> Assignee: Bartholdi Dominik
> Priority: Major
> Fix For: 1.9.1
>
>
> When using the jgit provider over http, it allows to define username /
> password like this:
> {code}
> mvn release:prepare release:perform -Dresume=false -Dusername=myuser
> -Dpassword=XXX
> {code}
> But the commit will not be done with the given user but with the system user
> who started the process, instead the passed user is only used for transport.
> Well that might be fine in the first thought, but it will mean in the git
> repository it is not recorded who really did make the release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
