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

Jakob Homan updated ZOOKEEPER-110:
----------------------------------

    Status: Patch Available  (was: Open)

I've modified the build.xml, replacing the previous svnant task with the same 
functionality using svntask (http://code.google.com/p/svntask/).  Svntask is 
apache-licensed, however, it relies on svnkit, which has an odd dual license 
(http://svnkit.com/licensing.html).  I'm not sure if this will create a 
licensing issue.  Not reflected in the patch is deleting the svnant directory 
in src/java/lib/ and adding a new directory, src/java/lib/svntask, that 
includes svnkit.jar and svntask.jar, obtained from the two sites above.  

Hope this is useful.

> 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
>
> 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