Chris Darroch updated ZOOKEEPER-474:

Interesting.  I'll try to take a look shortly.  The ironic thing is that you 
appear to have some intriguing but harmless compile warnings, and then the 
tests fail in one of the smallest tests (where we just try to work around the 
single log file from the C client), but pass all the complex ones!  So that's 
mostly good news, I think.

> add compile, test, and improved package targets to zkperl build.xml
> -------------------------------------------------------------------
>                 Key: ZOOKEEPER-474
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-474
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: contrib
>    Affects Versions: 3.2.0
>            Reporter: Chris Darroch
>            Assignee: Chris Darroch
>             Fix For: 3.2.1, 3.3.0
>         Attachments: zk474_testout.txt, ZOOKEEPER-474.patch
> This patch adds compile and test targets to the zkperl build.xml, and tweaks 
> the package target a little to use the manifest file.
> For me, "ant compile", "ant test", and "ant clean" all work (from scratch, in 
> each case) when using Ant in the local src/contrib/zkperl directory.
> Further, "ant package" in the top-level directory seems to continue to build 
> zkperl along with everything else, and leaves out the build.xml and 
> t/zkServer.sh files, which is appropriate.
> From what I can see, the top-level build.xml doesn't actually invoke the 
> test-contrib target, so I'm not sure if there's a way to integrate the zkperl 
> tests into the main hudson automated test process, but that would be ideal, 
> if at all possible.  I feel like I've seen comments to the effect that the 
> zkpython tests are run automatically, but I'm not sure if that's actually 
> true or not.

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