[
https://jira.codehaus.org/browse/SCM-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=324750#comment-324750
]
Robert Scholte commented on SCM-718:
------------------------------------
Almost: connectionUrl should stay as it is. Add
{{-Dmaven.scm.provider.svn.implementation=javasvn}} to your command (or set it
as property in the settings.xml) and add {{maven-scm-provider-svnjava-XXX.jar}}
to MAVEN_HOME/lib/ext/
That would be my guess, at least.
> Please include Java-based SVN client
> ------------------------------------
>
> Key: SCM-718
> URL: https://jira.codehaus.org/browse/SCM-718
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-svn
> Affects Versions: future
> Reporter: Markus KARG
> Assignee: Robert Scholte
>
> It is rather annoying that both major "Maven Embedders" (Eclipse IDE and
> Jenkins CI Server) are able to talk to SVN Servers without the need to have
> Subversion installed explicitly, but when running MVN:SCM mojos the same
> containers "inherit" Maven SCM's need for a native and explicitly installed
> Subversion client. :-(
> It would be so great if the SCM:SVN implementation would include a Java-based
> SVN client just as Eclipse and Jenkins do. For most use cases this would
> simplify the admin's job by far (think of a Jenkins CI build farm for
> example, where the admin currently needs to install SVN on each build slave),
> while all others could still explicitly disable the built-in Java-based
> client, effectively falling back to the current need of having SVN on disk.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
