maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SCM-718) Please include Java-based SVN client
Date Fri, 03 Jun 2016 22:11:59 GMT

     [ https://issues.apache.org/jira/browse/SCM-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Scholte resolved SCM-718.
--------------------------------
    Resolution: Not A Problem

Based on "no feedback" I assume this issue can be closed.

> Please include Java-based SVN client
> ------------------------------------
>
>                 Key: SCM-718
>                 URL: https://issues.apache.org/jira/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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message