ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alasdair Young <>
Subject Re: Odd Behavior
Date Wed, 03 Jan 2007 20:29:58 GMT
Fixed it. (I spent 2 hours on this, and just after I hit send, I realise
that there was one more place to check :)

cruise control has a cruisecontrol/lib directory with ant.jar in it. You
need to ensure that ant.jar, ant-junit.jar and junit.jar are all the
right versions and are all present in this directory.

- alasdair

Alasdair Young wrote:
> I'm currently attempting to set up cruise control just now and I agree
> with the high maintainance aspect. My plan once I am finished is to
> publish some step-by-step instrctions on getting subversion, CC, ant and
> junit all working nicely together under FC6.
> I have an issue right now where, if I run "ant -f cc-build.xml" (this
> downloads my source from svn, then calls the build script in another
> directory) from the command line, everything works, but if I have cruise
> control try, it gives me:
>> /root/cruise/cruisecontrol-bin-2.5/projects/builds/cc-build.xml:15:
>> The following error occurred while executing this line:
>> /root/cruise/cruisecontrol-bin-2.5/projects/builds/checkout/src/java/build.xml:45:
>> Could not create task or type of type: junit.
>> Ant could not find the task or a class this task relies upon.
>> This is common and has a number of causes; the usual
>> solutions are to read the manual pages then download and
>> install needed JAR files, or fix the build file:
>>  - You have misspelt 'junit'.
>>    Fix: check your spelling.
>>  - The task needs an external JAR file to execute
>>      and this is not found at the right place in the classpath.
>>    Fix: check the documentation for dependencies.
>>    Fix: declare the task.
>>  - The task is an Ant optional task and the JAR file and/or libraries
>>      implementing the functionality were not found at the time you
>>      yourself built your installation of Ant from the Ant sources.
>>    Fix: Look in the ANT_HOME/lib for the 'ant-' JAR corresponding to the
>>      task and make sure it contains more than merely a
>>      If all it contains is the manifest, then rebuild Ant with the needed
>>      libraries present in ${ant.home}/lib/optional/ , or alternatively,
>>      download a pre-built release version from
>>  - The build file was written for a later version of Ant
>>    Fix: upgrade to at least the latest release version of Ant
>>  - The task is not an Ant core or optional task
>>      and needs to be declared using <taskdef>.
>>  - You are attempting to use a task defined using
>>     <presetdef> or <macrodef> but have spelt wrong or not
>>    defined it at the point of use
>> Remember that for JAR files to be visible to Ant tasks implemented
>> in ANT_HOME/lib, the files must be in the same directory or on the
>> classpath
>> Please neither file bug reports on this problem, nor email the
>> Ant mailing lists, until all of these causes have been explored,
>> as this is not an Ant bug.
> I have checked every item in the list that was given. My $ANT_HOME
> definately has both ant-junit.jat and junit.jar in the lib directory. I
> am able to run junit tests via ant from the command line, butfor some
> reason when I run it through cruise control, I get this error.
> Does anyone have an idea where I can look?
> I appreciate this isn't cruise-control-users, but clearly people try to
> use CC and ant together.
> This is frustrating as I feel I am so close, yet I'm stumped.
> Also: will ant ever ship with things like subversion support, junit
> support, ssh/scp support as standard so that many of these issues can be
> avoided?
> Kind regards,
> - alasdair
> Steve Loughran wrote:
>> Res Pons wrote:
>>> Thanks for your reply.  I was using AnthillOS for a while but I gave
>>> up in frustration.  It's a kiddy tool for starters but very easy to
>>> use, however, the developers of it were so agonizingly slow to
>>> implement features, I gave up.  Now I'm reading on CruiseControl.  I
>>> read a bit about Maven but it seems to complicated and I'm a
>>> build/release engineer -  I found it an overkill.  But CC seems to be
>>> nice and up my alley.
>> We find CC a bit high-maintenance; I've been using luntbuild for a
>> while and am fairly happy with it.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message