[
https://issues.apache.org/jira/browse/SCM-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960081#comment-17960081
]
ASF GitHub Bot commented on SCM-13:
-----------------------------------
jira-importer commented on issue #322:
URL: https://github.com/apache/maven-scm/issues/322#issuecomment-2964585636
**[Emmanuel
Venisse](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=evenisse)**
commented
From TMate support :
Hello Emmanuel,
"file" protocol is already supported in development version in "trunk" and
will be included into version 1.1.0 that is currently planned to be
published in March 2006.
You may already use "file" protocol if you will checkout and build JavaSVN
from "http://svn.tmate.org/repos/jsvn/trunk/";. To enable "file" protocol,
you should first make the following call:
FSRepositoryFactory.setup(); // similar approach is used for DAV and svn
protocols support.
"file" protocol support pass mostly all python tests, but right now I would
not recommend you to use it against production repositories, and also it is
not yet optimized, so works somewhat slow.
> Investigate pure Java SVN interface
> -----------------------------------
>
> Key: SCM-13
> URL: https://issues.apache.org/jira/browse/SCM-13
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Task
> Components: maven-scm-provider-svn
> Reporter: Brett Porter
> Assignee: Emmanuel Venisse
> Priority: Major
> Fix For: 1.0-beta-3
>
> Attachments: SCM-13-maven-scm-api.patch,
> SCM-13-maven-scm-manager-plexus.patch, SCM-13-maven-scm-plugin.patch,
> SCM-13-maven-scm-provider-svn.tar.gz, ch.ethz.ganymed.tar.gz,
> tmate.org.javasvn.tar.gz
>
>
> There is this: http://tmate.org/svn/
> I'd say javahl is out because it requires native binaries.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
