On Thu, 19 Jul 2001 00:46, [EMAIL PROTECTED] wrote: > > Therefore, I would prefer an approach where the build file writer is > > explicit about which tasks should use the same loader. Something like > > > > <taskgroup> > > <classpath refid="blah"/> > > <taskdef name="foo" classname="com.foo.Foo"/> > > <taskdef name="bar" classname="com.foo.Bar"/> > > </taskgroup> > > > > Thoughts? > > That's the second half of the patch :-) ( taskdef with file= or resource=, > and all definitions loaded from a properties file with the same loader). > Same syntax/behavior as in Properties.
Instead of overloading taskdef I would prefer to see a new task. Perhaps tasksetdef or something? Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*
