The solution!!!, i think is a work around, just add to the jvm directives the following flag:"-Dmaven.scm.svn.config_directory=/path/to/.subversion", internally, when the engine finds this property, add to the svn line the argument "--config-dir", which is the folder when svn reads the configuration, the auth cache, etc
one note, is that the owner of the process of the server where is running continnum needs to accept the certificate permanently first (we can set the config-dir to other users/.subversion directory, but for avoid future problems, i think is better if we do it with the owner of the server process and use a self-owner/customsubversion directory) this could be avoid just with "svn list https://<address>/repo." and enter "p", i also add the issuer to the cacerts but it is not necessary Marco Mike Ahlers wrote: > > Hi, > > Just to add a comment. I have been in exactly the same situation, i.e. > self signed ssl with Continuum running in Jboss. I can confirm that having > a home directory with auth files is needed and solves the problem. > > Regards, > Mike > -- View this message in context: http://www.nabble.com/svn-over-self-signed-ssl-when-running-continuum-in-tomcat-tp17756569p18782515.html Sent from the Continuum - Users mailing list archive at Nabble.com.
