You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Berin Loritsch <bl...@apache.org> on 2003/04/14 14:19:39 UTC

[Fwd: [GUMP] Build Failure - excalibur-fortress]

Fortress is failing because it can't find a taskdef.  Here is what is
happening:

Fortress has a tools JAR file that it builds, and then uses that to
define a task to collect the meta information for the tests.  The
problem is that GUMP is not allowing it to use the task that Fortress
compiled.

How can I correct this?


-- 
"You know the world is going crazy when the best
rapper is a white guy, the best golfer is a black guy,
The Swiss hold the America's Cup, France is
accusing the US of arrogance, and Germany doesn't want
to go to war. And the 3 most powerful men in America
are named 'Bush', 'Dick', and 'Colon' (sic)".

-----Chris Rock

Re: [Fwd: Build Failure - excalibur-fortress]

Posted by Sam Ruby <ru...@apache.org>.
Berin Loritsch wrote:
> Fortress is failing because it can't find a taskdef.  Here is what is
> happening:
> 
> Fortress has a tools JAR file that it builds, and then uses that to
> define a task to collect the meta information for the tests.  The
> problem is that GUMP is not allowing it to use the task that Fortress
> compiled.
> 
> How can I correct this?

Add the following to the fortress definition:

     <work nested="fortress/build/tools">

http://jakarta.apache.org/gump/project.html#work

- Sam Ruby



Re: [Fwd: [GUMP] Build Failure - excalibur-fortress]

Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 14 Apr 2003, Berin Loritsch <bl...@apache.org> wrote:

> How can I correct this?

The jar most probably gets dropped from the classpath by the VM as it
doesn't exist when Ant is started.

The usual workaround is to use <work> to point to the directory with
the compiled classes and <mkdir> (in the Gump descriptor) to create
that directory before Ant is called.

Stefan

Re: [Fwd: Build Failure - excalibur-fortress]

Posted by Berin Loritsch <bl...@apache.org>.
Peter Donald wrote:
> On Mon, 14 Apr 2003 22:19, Berin Loritsch wrote:
> 
>>Fortress has a tools JAR file that it builds, and then uses that to
>>define a task to collect the meta information for the tests.  The
>>problem is that GUMP is not allowing it to use the task that Fortress
>>compiled.
>>
>>How can I correct this?
> 
> 
> put the directory on the classpath. To do this create a <work/> element (see 
> other descriptors for an example. Note you may also need to do a mkdir before 
> the ant task. May look something like
> 
> <mkdir dir="fortress/build/classes"/>
> ...
> 
> <depend .../>
> <work nested="build/classes"/>
> 

Ok, We'll see how it goes the next time around.



Re: [Fwd: Build Failure - excalibur-fortress]

Posted by Berin Loritsch <bl...@apache.org>.
Peter Donald wrote:
> On Mon, 14 Apr 2003 22:19, Berin Loritsch wrote:
> 
>>Fortress has a tools JAR file that it builds, and then uses that to
>>define a task to collect the meta information for the tests.  The
>>problem is that GUMP is not allowing it to use the task that Fortress
>>compiled.
>>
>>How can I correct this?
> 
> 
> put the directory on the classpath. To do this create a <work/> element (see 
> other descriptors for an example. Note you may also need to do a mkdir before 
> the ant task. May look something like
> 
> <mkdir dir="fortress/build/classes"/>
> ...
> 
> <depend .../>
> <work nested="build/classes"/>
> 

Ok, We'll see how it goes the next time around.



Re: [Fwd: Build Failure - excalibur-fortress]

Posted by Berin Loritsch <bl...@apache.org>.
Peter Donald wrote:
> On Mon, 14 Apr 2003 22:19, Berin Loritsch wrote:
> 
>>Fortress has a tools JAR file that it builds, and then uses that to
>>define a task to collect the meta information for the tests.  The
>>problem is that GUMP is not allowing it to use the task that Fortress
>>compiled.
>>
>>How can I correct this?
> 
> 
> put the directory on the classpath. To do this create a <work/> element (see 
> other descriptors for an example. Note you may also need to do a mkdir before 
> the ant task. May look something like
> 
> <mkdir dir="fortress/build/classes"/>
> ...
> 
> <depend .../>
> <work nested="build/classes"/>
> 

Ok, We'll see how it goes the next time around.



Re: [Fwd: Build Failure - excalibur-fortress]

Posted by Berin Loritsch <bl...@apache.org>.
Peter Donald wrote:
> On Mon, 14 Apr 2003 22:19, Berin Loritsch wrote:
> 
>>Fortress has a tools JAR file that it builds, and then uses that to
>>define a task to collect the meta information for the tests.  The
>>problem is that GUMP is not allowing it to use the task that Fortress
>>compiled.
>>
>>How can I correct this?
> 
> 
> put the directory on the classpath. To do this create a <work/> element (see 
> other descriptors for an example. Note you may also need to do a mkdir before 
> the ant task. May look something like
> 
> <mkdir dir="fortress/build/classes"/>
> ...
> 
> <depend .../>
> <work nested="build/classes"/>
> 

Ok, We'll see how it goes the next time around.


Re: [Fwd: [GUMP] Build Failure - excalibur-fortress]

Posted by Peter Donald <pe...@realityforge.org>.
On Mon, 14 Apr 2003 22:19, Berin Loritsch wrote:
> Fortress has a tools JAR file that it builds, and then uses that to
> define a task to collect the meta information for the tests.  The
> problem is that GUMP is not allowing it to use the task that Fortress
> compiled.
>
> How can I correct this?

put the directory on the classpath. To do this create a <work/> element (see 
other descriptors for an example. Note you may also need to do a mkdir before 
the ant task. May look something like

<mkdir dir="fortress/build/classes"/>
...

<depend .../>
<work nested="build/classes"/>

-- 
Cheers,

Peter Donald
*------------------------------------------------------*
| "The whole problem with the world is that fools and  |
| fanatics are always so certain of themselves, but    |
| wiser people so full of doubts." - Bertrand Russell  |
*------------------------------------------------------*