Dominique Devienne wrote: > Hummmm, not totally. If the AntLib also uses types, you need another > <typedef>, which should also probably needs a loaderref. Since you now use > twice the classpath, if needs to be outside and refid'd.
In ant1.6 the difference between tasks and types is very small. It would be trivial to load both of them at once. In any case, I don't quite agree with Stefan: the simpler solution is: <path id="..." /> <taskdef resource=".. " classpathref=".." /> I would love to completely remove the different treatment of types - i.e. a task is just like a type with an execute() method, and nothing else, and <taskdef> loades both kinds. That would be simpler than the current syntax that also require you to do a: <typedef resource="..." classpathref="..." /> Costin > > And what about the <junit> task? I'd like to not have setup my classpath > outside of Ant and build.xml, and avoid having to dump everything in > AntLib. > > I believe it can and should be easier and more flexible. --DD > > -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 26, 2003 10:27 AM > To: [EMAIL PROTECTED] > Subject: Re: Artima SuiteRunner Task > > On Wed, 26 Mar 2003, Dominique Devienne <[EMAIL PROTECTED]> wrote: > >> That said (one more ;-), if Ant ever comes up with an easier way to >> integrate third party tasks > > Easier than <taskdef resource="..."><classpath .../></taskdef>? > > Almost impossible. > > Stefan
