[
https://issues.apache.org/jira/browse/SCM-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962731#comment-17962731
]
ASF GitHub Bot commented on SCM-718:
------------------------------------
jira-importer opened a new issue, #929:
URL: https://github.com/apache/maven-scm/issues/929
**[Markus
Karg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mkarg)**
opened
**[SCM-718](https://issues.apache.org/jira/browse/SCM-718?redirect=false)** and
commented
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.
---
**Affects:** future
> Please include Java-based SVN client
> ------------------------------------
>
> Key: SCM-718
> URL: https://issues.apache.org/jira/browse/SCM-718
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-svn
> Affects Versions: future
> Reporter: Markus Karg
> Assignee: Robert Scholte
> Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
