[
https://issues.apache.org/jira/browse/SCM-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961182#comment-17961182
]
ASF GitHub Bot commented on SCM-366:
------------------------------------
jira-importer commented on issue #585:
URL: https://github.com/apache/maven-scm/issues/585#issuecomment-2964605340
**[Christian
Nelson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=xianpants)**
commented
JavaSVN's license has changed since the original discussion around issue
SCM-13. Is the current license still prohibitive?
The maven release plugin is very brittle under non-unix platforms because of
its dependency on the svn binary. I imagine switching to an all-Java SVN
client could also simplify unix usage as well. I'd be stoked to see this
happen and help out if the licensing issue is now a non-issue.
> Provide pure-java svn implementation
> ------------------------------------
>
> Key: SCM-366
> URL: https://issues.apache.org/jira/browse/SCM-366
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Wish
> Components: maven-scm-provider-svn
> Affects Versions: 1.2
> Reporter: Florian Kirchmeir
> Assignee: Olivier Lamy
> Priority: Minor
>
> Please remove the dependency on the svn.exe command-line executable!
> See http://jira.codehaus.org/browse/SCM-13:
> The issue has been closed as "FIXED", but the maven-scm-provider-svnjava
> module appearently has never been comitted.
> Thanks!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
