[
https://issues.apache.org/jira/browse/SCM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962748#comment-17962748
]
ASF GitHub Bot commented on SCM-727:
------------------------------------
jira-importer opened a new issue, #933:
URL: https://github.com/apache/maven-scm/issues/933
**[Dominik
Richner](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=domi)**
opened
**[SCM-727](https://issues.apache.org/jira/browse/SCM-727?redirect=false)** and
commented
Providing a scm-provider based on jgit would provide quite some advantages
over the cgit implementation when working with git:
* no native client to be installed
* support of username/password authentication (e.g. to GitHub)
* ...
I have an a running and tested implementation done a placed a pull request
on GitHub: https://github.com/apache/maven-scm/pull/5
---
**Issue Links:**
- [SCM-503](https://issues.apache.org/jira/browse/SCM-503) create a native
Java GIT provider using JGit
> integrate scm-provider based on jgit
> ------------------------------------
>
> Key: SCM-727
> URL: https://issues.apache.org/jira/browse/SCM-727
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: maven-scm-provider-gitexe
> Reporter: Dominik Richner
> Assignee: Olivier Lamy
> Priority: Major
> Fix For: 1.9
>
>
> Providing a scm-provider based on jgit would provide quite some advantages
> over the cgit implementation when working with git:
> * no native client to be installed
> * support of username/password authentication (e.g. to GitHub)
> * ...
> I have an a running and tested implementation done a placed a pull request on
> GitHub: https://github.com/apache/maven-scm/pull/5
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
