> -----Original Message-----
> From: Antoine Levy-Lambert [mailto:[EMAIL PROTECTED]
> > From: "Conor MacNeill" <[EMAIL PROTECTED]>
> > 1. <import>
>
> I would also go for it as it is.
+1. I'm awaiting <import> eagerly too.
> > 2. antlib
>
> I have not tested it myself, but we need to release the feature to
> see how good it is. I am optimistic that it will work.
+0. I'm not sure AntLib should be released without a real world use of it
directly in Ant or Ant-Contrib for example. Converting all of ant-optional
to AntLib would be a huge undertaking, but it has to start somewhere.
Once stuff is released, there's this backward-compatibility thing...
> > 3. <macrodef> and <presetdef>
> >
> Would go for releasing them, with an "experimental" warning in
> the manual pages. If we do not release these tasks, we won't get
> any feedback as to whether they are generally useful, or whether
> their build file interface is easy to use, or whether they contain
> unwanted features.
I don't think there's such a thing as experimental stuff. It's either in or
not, and once in, it must be backward compatible.
I'm sorry so few people chimed in on the subject of overloading the meaning
of ${name} in Ant. If this could be changed, then I'd have an enthusiastic
+1, but as it stands, I'm -1 or maybe -0.
--DD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
