Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of m.v.lunteren@gmail.com
 designates 64.233.182.185 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=Saz5wISo7p9kP8Ung5cPFXAmo9iUZzvdZBREmnkJHRJOfkxyZwzr4CfGc5lHWKaDaO
         y8+Ms170pvlbak4gISbh571EpcStxk2WhKq+W607RKGUQ6F6xm0lGi0wFkHNHU/jaCti
         r0CNSw2I/+Lim8EUB6XpNAcQcvcJw7mIcXlxU=
Message-ID: <c25576af0810160900o69cb2b4fmcb49544a53bee128@mail.gmail.com>
Date: Thu, 16 Oct 2008 09:00:28 -0700
From: "Myrna van Lunteren" <m.v.lunteren@gmail.com>
To: derby-dev@db.apache.org
Subject: Re: Build Report - tinderbox_trunk16 705255 build failed - Sun
 Database Engineering [Auto-generated mail]
In-Reply-To: <20081016144506.17232.qmail@nanna30>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20081016144506.17232.qmail@nanna30>

> checkjunittask:
>
> junit-init:
>    [mkdir] Created dir: Apache/TinderBox_Derby/trunk/junit_20081016_1645/testout
>
> runmessagechecktest:
>
> junit-init:
>
> junit-single:
>
> BUILD FAILED
> Apache/TinderBox_Derby/trunk/build.xml:479: The following error occurred while executing this line:
> Apache/TinderBox_Derby/trunk/build.xml:2136: 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 META-INF/MANIFEST.MF.
>     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 apache.org
>  - 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.
>
> Total time: 7 minutes 4 seconds
>
>

This is due to my changes for DERBY-1458 again.
I'm really puzzled now. I guess I'll have to implement the test
without the junit ant task after all.

I'll remove the dependency again, but to satisfy my curiosity, if
someone can maybe figure out why on this particular machine the junit
task doesn't work I'd appreciate it.

Myrna