> -----Original Message----- > From: Sam Ruby [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 10, 2001 1:41 PM > To: [EMAIL PROTECTED] > Subject: Re: PROPOSAL: loading tasks from jars for Ant 1.5 > > > Ovidiu Predescu wrote: > > > > A simpler solution to the one proposed above is to this is to allow > > antlib to appear inside a <target> element. This way one > can write the > > build.xml file that builds a new antlib in a target, and > makes use of > > it in another target. Something like this: > > [snip] > > I'm not sure what are the implications with the current class loader > > mechanisms, but a solution can probably be worked out. > > I believe that some of the Ant 2.x designs are conducive to such an > approach, but the last time I looked, this was problematic > with the current > design. > > The root problem is (was?) that tasks objects are created and > then executed > one by one. It is hard to create a strongly typed task > object when the > task has not been defined just yet.
Maybe I'm not following, but that would be a problem today, wouldn't it? You could always try to call a task before you define it, and Ant would fail. Defining the task with <antlib> would work just like defining the task with <taskdef> and then using it afterwards. Tim
