[
https://issues.apache.org/jira/browse/SCM-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964325#comment-17964325
]
Olivier Lamy commented on SCM-185:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#456|https://github.com/apache/maven-scm/issues/456].
> Validity check rejects valid protocol
> -------------------------------------
>
> Key: SCM-185
> URL: https://issues.apache.org/jira/browse/SCM-185
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Affects Versions: 1.0-beta-2
> Reporter: Joerg Schaible
> Assignee: Emmanuel Venisse
> Priority: Major
> Fix For: 1.0-rc1
>
>
> According to the subversion manual a user can add arbitrary protocols by
> defining new tunnels in his local subversion configuration. Such definitions
> are necessary to tunnel ports, define the usage of a smart card, ... e.g.
> defining an entry in the tunnel section of the .subversion/config file to
> access over SSH protocol version 1 can be defined like:
> ssh1=ssh -1
> A repo would be accessed with "svn+ssh1://repo/url"
> This is not possible, since the SvnScmProvider checks against a fixed set of
> protocols, which is not correct.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
