Owen O'Malley commented on ZOOKEEPER-110:

My reading of the svnkit license would make it incompatible with the Apache 
license. If it is incompatible, you can not depend on it or distribute it as 
part of Zookeeper. See http://www.apache.org/legal/3party.html . If there isn't 
away to avoid svnkit or fix svnant, you can ask legal about the TMate license. 
In my opinion, the clause that will be fatal is:

  * Redistribution in any form without redistributing source code for software 
      that uses SVNKit is possible only when such redistribution is explictly 
      by TMate Software. Please, contact TMate Software at [EMAIL PROTECTED] to 
      get such permission.

which is effectively a GPL-like viral clause with an escape clause that lets 
TMate give/sell exceptions.

> Build script relies on svnant, which is not compatible with subversion 1.5 
> working copies
> -----------------------------------------------------------------------------------------
>                 Key: ZOOKEEPER-110
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-110
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 3.0.0
>         Environment: Subversion 1.5 command line, or subclipse version 1.4.x
>            Reporter: Jakob Homan
>         Attachments: svntask.diff
> The current build.xml ant script uses svnant to obtain the latest revision 
> number from the repo, however svnant is not compatible with subversion 1.5 
> (http://subversion.tigris.org/svn_1.5_releasenotes.html), and so the build 
> fails with working copies checked out by this version.  The build fails with 
> "this version of subversion is too old, please get a newer version..."  This 
> will become more apparent as svn 1.5 trickles out; I'm using a brand new dev 
> environment with both subclipse 1.4 and svn 1.5 client, so I got bit rather 
> quickly.
> Those with svn 1.5 can get the code from the trunk, but cannot do an ant 
> build.
> svnant hasn't been updated in more than a year and appears to be dead, so it 
> may no longer be a viable tool for the ant build.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to