RE: [Xdoclet-devel] Making XDoclet more modular

[Aslak Hellesøy <as...@netcom.no>]

I don't have time to follow ant-dev really, but here is the POC that uses
BCEL to add create methods to the task on the fly. Perhaps something you can
integrate into the Ant core somehow?

(In case the mail to ant-dev gets bounced, please forward it Andrew)

Aslak (from XDoclet dev team)

> -----Original Message-----
> From: Erik Hatcher [mailto:lists@ehatchersolutions.com]
> Sent: 5. april 2002 06:29
> To: Aslak Hellesoy; Ara Abrahamian
> Cc: xdoclet-devel@lists.sourceforge.net
> Subject: Re: [Xdoclet-devel] Making XDoclet more modular
>
>
> *wow*.... over my head.  I suggest you hop over to the ant-dev e-mail list
> to discuss the Ant class loader issues in more detail.
>
> But one comment:
>
> > The issue is how do we tell Ant to use the instrumenting class loader? I
> > have taken a brief look at Ant's Taskdef and its Definer. I
> think we need
> to
> > subclass Taskdef and override the execute() method to use our own class
> > loader. It means that we'll need 2 taskdefs to use XDoclet this
> way (until
> > the Ant guys make it simpler for us).
> >
> > <taskdef name="xtaskdef" classname="xdoclet.XTaskdef"/>
> > <xtaskdef name="ejbdoclet" classname="xdoclet.ejb.EjbDocletTask"/>
>
> You wouldn't need two taskdefs: if you're going to create a <xtaskdef> it
> could just do the work internally that the first one you show does also.
>
> Ara has never integrated in my suggestion of having XDoclet itself build a
> properties file:
>
> ejbdoclet=xdoclet.ejb.EjbDocletTask
> .
> .
> .
>
> And embedding that into xdoclet.jar.
>
> Then you could do this:
>
>     <taskdef resource="taskdef.properties"
> classpathref="xdoclet.classpath"/> - that would keep folks from having to
> know classnames, and they could change from one version to another without
> breaking anyones build files.
>
> I'm currently using XDoclet to build this properties file
> dynamically for me
> from @ant:task name="bla" tags.
>
>     Erik
>
>
>