[
https://issues.apache.org/jira/browse/SCM-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961186#comment-17961186
]
ASF GitHub Bot commented on SCM-366:
------------------------------------
jira-importer commented on issue #585:
URL: https://github.com/apache/maven-scm/issues/585#issuecomment-2964605343
**[Siveton
Vincent](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=siveton)**
commented
The maven-scm-provider-svnjava is already present in our sandbox [1]. I
migrated code to the latest SCM API in
[r691600](http://svn.apache.org/viewvc?rev=691600&view=rev).
Some methods are not implemented yet., patch welcomes :)
[1]
http://svn.apache.org/repos/asf/maven/sandbox/trunk/scm/maven-scm-provider-svnjava
> Provide pure-java svn implementation
> ------------------------------------
>
> Key: SCM-366
> URL: https://issues.apache.org/jira/browse/SCM-366
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Wish
> Components: maven-scm-provider-svn
> Affects Versions: 1.2
> Reporter: Florian Kirchmeir
> Assignee: Olivier Lamy
> Priority: Minor
>
> Please remove the dependency on the svn.exe command-line executable!
> See http://jira.codehaus.org/browse/SCM-13:
> The issue has been closed as "FIXED", but the maven-scm-provider-svnjava
> module appearently has never been comitted.
> Thanks!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
