[
https://jira.codehaus.org/browse/SCM-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349986#comment-349986
]
Karl-Heinz Marbaise commented on SCM-765:
-----------------------------------------
seemed to be fixed by git commit:
[037ba69bced119de1618526e6977940908eeb7bc|https://github.com/apache/maven-scm/commit/037ba69bced119de1618526e6977940908eeb7bc]
> jgit provider commits changes with system user instead of passed username
> -------------------------------------------------------------------------
>
> Key: SCM-765
> URL: https://jira.codehaus.org/browse/SCM-765
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.9
> Reporter: Dominik Bartholdi
> Assignee: Dominik Bartholdi
> Fix For: 1.10
>
>
> 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
(v6.1.6#6162)
