hadoop-zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Hunt (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ZOOKEEPER-110) Build script relies on svnant, which is not compatible with subversion 1.5 working copies
Date Wed, 06 Aug 2008 16:06:46 GMT

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

Patrick Hunt updated ZOOKEEPER-110:
-----------------------------------

    Assignee: Jakob Homan
      Status: Open  (was: Patch Available)

I'm +1 on this change, -1 on using svntask re the issues Owen mentioned.

Jakob -- notice that Hadoop core does something very similar, however they use a script, could
you reuse this rather than relying on a third party library?

http://svn.apache.org/repos/asf/hadoop/core/trunk/build.xml
    <exec executable="sh">
       <arg line="src/saveVersion.sh ${version}"/>
    </exec>
http://svn.apache.org/repos/asf/hadoop/core/trunk/src/saveVersion.sh



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


Mime
View raw message