[ https://issues.apache.org/jira/browse/ZOOKEEPER-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620404#action_12620404 ]
Patrick Hunt commented on ZOOKEEPER-110: ---------------------------------------- I noticed this in the ant exec manpage: Cygwin Users The <exec> task will not understand paths such as /bin/sh for the executable parameter. This is because the Java VM in which Ant is running is a standard Windows executable and is not aware of the Cygwin environment (i.e., doesn't load cygwin1.dll). The only work-around for this is to compile a JVM under Cygwin (at your own risk). See for instance sun jdk 6 build instructions for cygwin. I created a simple build.xml and regardless of whether I run under cmd or cygwin bash I still get "Windows XP" as the os.name. What about Mac users, are they covered as well? > 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 > Assignee: Jakob Homan > Attachments: revthrushell.diff, 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.