Yeah, it's done. There is actually a copy of the lib
checked-in as ivy/ivy-2.2.0.jar: it does not need to download it
(a subtle details I forgot about). "ivy-init-antlib" just adds
the lib to the class path.

Thanks,
Sebastian

On 07/05/2014 10:04 AM, DigitalPebble wrote:
> Thanks for looking into this and having fixed it Seb! 
> 
> Julien
> 
> 
> On 4 July 2014 08:51, Sebastian Nagel <[email protected]
> <mailto:[email protected]>> wrote:
> 
>     Hi,
> 
>     I'm able to reproduce the problem with failing trunk builds on Jenkins:
> 
>     1. ant clean
>     2. rm ~/.ant/lib/ivy-2.2.0.jar (or wherever ant caches the ivy lib)
>     3. ant nightly
> 
>     The reason is that the target "resolve-test" does not depend on "init"
>     which will make sure that the ivy lib gets installed (it transitively 
> depends
>     on "ivy-download"/"ivy-prob-antlib").
> 
>     Cf. first targets of last successfull build and last failing build:
>      https://builds.apache.org/job/Nutch-trunk/2679/consoleFull
>      https://builds.apache.org/job/Nutch-trunk/2685/console
> 
>     So, we must place "init" somewhere in the dependency chain/tree of "test",
>     presumably as first dependency of "compile-core-test", in parallel to 
> "compile-core".
>     Right?
> 
>     I'll fix it over the weekend. But if anybody is faster... You're welcome!
> 
>     Cheers,
>     Sebastian
> 
>     2014-07-02 17:49 GMT+02:00 Sebastian Nagel <[email protected]
>     <mailto:[email protected]>>:
> 
>         Build and tests run successfully on my local machine.
>         But it repeatedly fails on ubuntu* Jenkins machines.
>         The error in resolve-test could be related to
>         - changes to test dependencies (NUTCH-1802, NUTCH-1803)
>         - or missing ivy libs in ant installations
> 
>         Any ideas? 
> 
>         Sebastian
> 
>         2014-07-02 6:33 GMT+02:00 Apache Jenkins Server 
> <[email protected]
>         <mailto:[email protected]>>:
> 
>             See <https://builds.apache.org/job/Nutch-trunk/2683/>
> 
>              
> 
>             Started by timer
>             Building remotely on ubuntu3 
> <https://builds.apache.org/computer/ubuntu3> (Ubuntu ubuntu) in workspace 
> /home/jenkins/jenkins-slave/workspace/Nutch-trunk
> 
>         ...
> 
>             At revision 1607241
>             no change for http://svn.apache.org/repos/asf/nutch/trunk since 
> the previous build
>             [trunk] $ /home/hudson/tools/ant/latest/bin/ant -file build.xml 
> nightly javadoc
>             Buildfile: 
> /x1/jenkins/jenkins-slave/workspace/Nutch-trunk/trunk/build.xml
>             Trying to override old definition of task javac
>               [taskdef] Could not load definitions from resource 
> org/sonar/ant/antlib.xml. It could
>             not be found.
> 
>             clean-lib:
> 
>             resolve-test:
> 
>             BUILD FAILED
>             
> /x1/jenkins/jenkins-slave/workspace/Nutch-trunk/trunk/build.xml:477: Problem: 
> failed to
>             create task or type antlib:org.apache.ivy.ant:resolve
>             Cause: The name is undefined.
>             Action: Check the spelling.
>             Action: Check that any custom tasks/types have been declared.
>             Action: Check that any <presetdef>/<macrodef> declarations have 
> taken place.
>             No types or tasks have been defined in this namespace yet
> 
>             This appears to be an antlib declaration.
>             Action: Check that the implementing library exists in one of:
>                     -/home/hudson/tools/ant/latest/lib
>                     -/home/jenkins/.ant/lib
>                     -a directory added on the command line with the -lib 
> argument
> 
> 
>             Total time: 0 seconds
>             Build step 'Invoke Ant' marked build as failure
>             Publishing Javadoc
> 
> 
> 
> 
> 
> 
> -- 
> ****
> ** 
> *Open Source Solutions for Text Engineering
>  
> http://www.digitalpebble.com*
> *http://digitalpebble.blogspot.com <http://digitalpebble.blogspot.com/>**
> *
> https://twitter.com/digitalpebble*
> *

Reply via email to