[
https://issues.apache.org/jira/browse/SCM-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960090#comment-17960090
]
ASF GitHub Bot commented on SCM-13:
-----------------------------------
jira-importer commented on issue #322:
URL: https://github.com/apache/maven-scm/issues/322#issuecomment-2964585640
**[Emmanuel
Venisse](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=evenisse)**
commented
From TMate support:
Forgot one more thing to mention - JavaSVN only supports repositories of
type 'fsfs'. This is a default type of repository, and probably most widely
used, but there are aslo 'bdb' (berkley db based) repositories that are not
supported, and so far there are no plans to support them.
> 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)
