[
https://issues.apache.org/jira/browse/SCM-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960085#comment-17960085
]
ASF GitHub Bot commented on SCM-13:
-----------------------------------
jira-importer commented on issue #322:
URL: https://github.com/apache/maven-scm/issues/322#issuecomment-2964585633
**[David
Hawkins](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dhawkins)**
commented
I forgot to mention authentication. In order to get authentication
information into the JavaSVN library, I added the ability for the svn provider
to look up authentication information in the user's settings.xml. It attempts
to locate a server with the appropriate id. If found, it will use that
username, password, private key, passphrase, etc. when authenticating. This is
the comment block from the method which attempts to find an appropriate server
id:
Attempt to look up the username/password from the user's maven settings
file.
Start with the full url and work backwards for each directory until we have
only
the host name. Then do the same pattern again without the protocol.
Example:
http://svn.mydomain.com/myrepo/myproject
http://svn.mydomain.com/myrepo
http://svn.mydomain.com
svn.mydomain.com/myrepo/myproject
svn.mydomain.com/myrepo
svn.mydomain.com
> 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)
