Hi all, Svnkit can read subversion's native configuration files in the .subversion directory, and this seems to work fine. The Jenkins Subversion plugin, which uses svnkit, cannot read the subversion native configuration files in the .subversion directory, nor can it support client certificates on slaves, and I am trying to patch the plugin to work like svnkit does and just read the native subversion config files.
I am confused about exactly how svnkit implements the native subversion configuration directory. I have found the http://svnkit.com/javadoc/org/tmatesoft/svn/core/auth/SVNAuthentication.html class, which gives me 4 different implementations, password, ssh, ssl and username. These are the four options used by the jenkins subversion plugin. Which of these four classes (if any) should I be using if I just want to revert to the native subversion config files and nothing else? Am I looking at the right code? What I want svnkit to do is connect to a repository, following the native subversion client's exact behaviour of reading and parsing .subversion/servers to work out the credentials to send to the server. I want to completely disable any attempt by Jenkins to fiddle with credentials. Would it be possible to show me what code I should be using to do this? Regards, Graham --
smime.p7s
Description: S/MIME cryptographic signature
