[
https://issues.apache.org/jira/browse/SCM-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964597#comment-17964597
]
Olivier Lamy commented on SCM-178:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#362|https://github.com/apache/maven-scm/issues/362].
> maven-scm-provider-git
> ----------------------
>
> Key: SCM-178
> URL: https://issues.apache.org/jira/browse/SCM-178
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: New Feature
> Affects Versions: 1.0-beta-2
> Reporter: Dominik Winter
> Priority: Minor
> Attachments: GIT.txt
>
>
> Please find the git provider as attachment.
> The diff command is not yet implemented, I'll do that on weekend.
> The update command is not supported, use the checkout command.
> The JUnit tests are "proprietary", not yet TCK. I'll do that. Maybe not on
> this weekend ;-)
> I used the git provider together with maven-release-plugin, it works fine for
> that use case.
> If you want to run the tests, you must have git installed and it must be in
> your PATH.
> To run git:
> - on Windows: use Cygwin and install the binutils, openssh, openssl, rsync,
> curl
> than you are able to compile and install git
> - on Linux: there are packages somewhere
> - on Mac OS X: use the DarwinPorts
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
