[
http://jira.codehaus.org/browse/MRELEASE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MRELEASE-344.
---------------------------------
Assignee: Olivier Lamy
Resolution: Won't Fix
You can use maven-scm-provider-svnjava.
See http://code.google.com/p/maven-scm-provider-svnjava/.
Add this artifact in the release plugin dependency.
Then in the plugin configuration :
{code:xml}
<providerImplementations>
<svn>javasvn</svn>
</providerImplementations>
{code}
> Make this plugin use SVNKit
> ---------------------------
>
> Key: MRELEASE-344
> URL: http://jira.codehaus.org/browse/MRELEASE-344
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Components: scm
> Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5, 2.0-beta-6,
> 2.0-beta-7
> Reporter: Michael Osipov
> Assignee: Olivier Lamy
>
> Right now the release plugin realies on the svn client installed on the
> system which breaks somehow maven's and Java's protability.
> Why not use SVNKit to perform release related tasks with SVN?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
