[
https://issues.jenkins-ci.org/browse/JENKINS-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160488#comment-160488
]
Jose Pedro Correia commented on JENKINS-8871:
---------------------------------------------
Hi fcamblor,
Thanks for the feedback (I just saw it now, sorry).
I tried out that test job. It worked fine. However, I still have exactly the
same problem...
> Allow to use other SVN protocol than http/https
> -----------------------------------------------
>
> Key: JENKINS-8871
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8871
> Project: Jenkins
> Issue Type: Improvement
> Components: scm-sync-configuration
> Reporter: fcamblor
> Assignee: fcamblor
> Attachments: scm-sync-configuration-0.0.5-bugfix8871-1.hpi
>
>
> Prior to v0.0.3, scm-sync-configuration plugin is relying on svnjava maven
> scm provider (see
> http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/ ),
> only http/https/file protocols are supported (for example svn+ssh is not
> supported).
> Eventually, a workaround would be to activate svnexe maven scm implementation
> for these case (Problem is : I don't know if we can have both svnexe &
> svnjava plexus component activated in the same time)
> Nevertheless, the best point would be to have svnjava be compliant with every
> svn supported protocols.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
