Re: Taskdef Event Bug?

Hi Paul,

I have seen this and am not entirely sure why it happens, but there seems 
to be a simple workaround.  When you define the taskdef you provide the 
classpath.  Now, also define the classpath for the <events> tag.  Again, I 
don't know why this is necessary, but it seems to do the trick.  The 
BarracudaDiscRack build.xml is set up like this...

         <taskdef
             name="events"
             classname="org.enhydra.barracuda.taskdefs.EventBuilder" >
             <classpath refid="build.classpath" />
         </taskdef>

         <events
             srcdir="${build.event_source.dir}"
             destdir="${build.classes.dir}"
             descriptor="${src.dir}/${src.package.path}${subdir}" >
             <classpath refid="build.classpath" />
         </events>

What is weird is that the main Barracuda build.xml doesn't require the 
classpath for the <events> tag, but if it is left out for BarracudaDiscRack 
(or any other build I've done separately from Barracuda), things go 
haywire, like you've described.

Anyway, try that workaround and let me know if you still have 
troubles.  Patches to fix this issue are definitely welcome :-)  Otherwise, 
it isn't overly important to fix since the workaround is so simple.

Jake

At 10:52 PM 7/29/2003 +0200, you wrote:
>Hi Guys,
>
>I tried to create an own slim ant project for my barracuda sources and got a
>crazy error while compiling the generated events with the taskdef "events".
>It can't find all barracuda classes of the specified classpathref although it
>is correctly given to the taskdef environment. Can't understand this because
>the class Event inherits from Javac. If I put all the barracuda classes into
>the destdir of the compiler, it works.
>
>But this seems to be a bug, because I would like to use my own jars in the
>classpath ...
>
>Thanks in advance,
>
>  Paul
>
>_______________________________________________
>Barracuda mailing list
>[email protected]
>http://barracudamvc.org/lists/listinfo/barracuda