You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christian Nelson (JIRA)" <ji...@codehaus.org> on 2008/07/14 18:20:26 UTC

[jira] Commented: (SCM-366) Provide pure-java svn implementation

    [ http://jira.codehaus.org/browse/SCM-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=141727#action_141727 ] 

Christian Nelson commented on SCM-366:
--------------------------------------

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: http://jira.codehaus.org/browse/SCM-366
>             Project: Maven SCM
>          Issue Type: Wish
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.0
>            Reporter: Florian Kirchmeir
>            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 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