[ http://jira.codehaus.org/browse/SCM-13?page=comments#action_54475 ]
David Hawkins commented on SCM-13: ---------------------------------- 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: http://jira.codehaus.org/browse/SCM-13 > Project: Maven SCM > Type: Task > Components: maven-scm-provider-svn > Reporter: Brett Porter > 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 is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
