Namespaces is important to me. For example, my <subant> task infers the current target name, whereas this feature was removed from the version now checked in to Ant. I should be able to not have to rename it, and use it as <lgc:subant> for example.
Of course, this will force me to update numerous builds (OK, only about 20 as of now), so the ability to cleanly override the version of <subant> from core would be nice too (no warning message). On the other hand, it would probably be a good thing to add the lgc: namespace to all our custom tasks in all our build files. It makes it clear these are custom tasks (I was asked a few times whether tasks where custom or Ant core, since we use quite a few custom tasks). People might feel using namespaces is too verbose, but I think that on the contrary it makes the build file more explicit and readable. --DD > -----Original Message----- > From: peter reilly [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 26, 2003 6:40 AM > To: Ant Developers List > Subject: Re: Ant 1.6 todo thoughts > > Ok: > 1) polymorphism > 2) loading of antlib.xml files/resource > 3) namespace > 4) roles > > Peter > > On Wed, 2003-06-25 at 10:25, Stefan Bodewig wrote: > > On 25 Jun 2003, peter reilly <[EMAIL PROTECTED]> wrote: > > > > > The roadmap could be: > > > 1) roles (allowing the typedef definition to be optionally > > > restricted - this is required to allow current conditions > > > /filters etcs to be defined) (+ extendtype) > > > 2) polymorphism (using ant-type magic attribute) > > > 3) loading of an antlib.xml file/resource. > > > 4) namespace support > > > > > > I could reorder these - or combine them. > > > > Please don't combine but do them one by one so the changes are easier > > to audit. Of those points roles is the most contoversial one IIUC - > > it may make sense to move it to the bottom so the discussion won't > > hold up the rest. > > > > Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
