Re: Taskdef Event Bug?

Hi Jacob,

thanks, it works. Now this sounds more plausible to me.

The first classpathref is only to look for the "taskdef" class.
The second classpathref is the build class path for all source files.
Ant seems to use two different classloaders for this ...

bye, Paul 

Zitiere Jacob Kjome <[email protected]>:

> 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>