Re: AW: Vote: local for 1.6
On Wednesday 22 October 2003 08:41, Antoine Lévy-Lambert wrote: I am OK for the third beta. In the third beta we should have : - the local properties, - a new xml-apis.jar (probably the one which is distributed with Xerces-Java 2.5) - can we also have the endorsed libraries ? - other points ? * there was some discussion on the namespace support - - should the default uri be antlib:org.apache.tools.ant to be consistent with other antlib uri's + I had argued before that it should not, but now I think it should. - should the uris of introspection discovered nested elements be the same as the containing task + I am not too sure about this, the current state is more readable and easy to get right but the proposed change would be easier to automate for syntax directed editors. * antlib support - should typedef resource=x/ look for all instances of x or just the first one. + I think it should. Once these changes are done - hopefully soon - we will set new dates (for the third beta and for 1.6.0) Cheers, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: AW: Vote: local for 1.6
From: peter reilly [mailto:[EMAIL PROTECTED] On Wednesday 22 October 2003 08:41, Antoine Lévy-Lambert wrote: I am OK for the third beta. In the third beta we should have : - the local properties, - a new xml-apis.jar (probably the one which is distributed with Xerces-Java 2.5) - can we also have the endorsed libraries ? - other points ? * there was some discussion on the namespace support - - should the default uri be antlib:org.apache.tools.ant to be consistent with other antlib uri's + I had argued before that it should not, but now I think it should. * antlib support - should typedef resource=x/ look for all instances of x or just the first one. + I think it should. Two remarks: 1) If, as I hope, the Ant namespace URI changes to antlib:org.apache.tools.ant, then an antlib.xml would be available there. For consistency's sake, but also because of (2) below... 2) This Ant antlib.xml would of course reference the existing tasks/types properties files, but *additionally* declare all the little types, like selectors, mappers, etc... Without (2), I cannot right a custom task with a new add(FilenameSelector) introspection point (or add(Condition), etc..), and be able to use the built-in Ant selectors, conditions, etc... (at least not without an explicit declaration for them somewhere.) It would be really strange to be able to use such custom types (selectors, mappers, conditions, etc...) as usual in Ant 1.6, but not the Ant built-in ones. --DD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Vote: local for 1.6
On Thursday 23 October 2003 15:16, Dominique Devienne wrote: From: peter reilly [mailto:[EMAIL PROTECTED] On Wednesday 22 October 2003 08:41, Antoine Lévy-Lambert wrote: I am OK for the third beta. In the third beta we should have : - the local properties, - a new xml-apis.jar (probably the one which is distributed with Xerces-Java 2.5) - can we also have the endorsed libraries ? - other points ? * there was some discussion on the namespace support - - should the default uri be antlib:org.apache.tools.ant to be consistent with other antlib uri's + I had argued before that it should not, but now I think it should. * antlib support - should typedef resource=x/ look for all instances of x or just the first one. + I think it should. Two remarks: 1) If, as I hope, the Ant namespace URI changes to antlib:org.apache.tools.ant, then an antlib.xml would be available there. For consistency's sake, but also because of (2) below... 2) This Ant antlib.xml would of course reference the existing tasks/types properties files, but *additionally* declare all the little types, like selectors, mappers, etc... A couple of proplems with this: * roles are not implemented in ant 1.6 so there is no way to disguish or as a condition, or as a selector - etc * mappers are not yet implemented in this way * antlib.xml for ant core/optional would be quite large and some work would need to be done to speed up loading from and antlib. Without (2), I cannot right a custom task with a new add(FilenameSelector) introspection point (or add(Condition), etc..), and be able to use the built-in Ant selectors, conditions, etc... (at least not without an explicit declaration for them somewhere.) One needs to extend the current container base classes (o.a.t.ant.taskdefs.condition.ConditionBase) or implement the current container interfaces ( (o.a.t.ant.types.selector.SelectorContainer). But this is not a nice situation... Peter It would be really strange to be able to use such custom types (selectors, mappers, conditions, etc...) as usual in Ant 1.6, but not the Ant built-in ones. --DD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Vote: local for 1.6
-0 (don't object enough to veto it) I would like to put the local property patch into ant 1.6. Normally I would wait for 1.7 for this, but it has a big and (I think) beneficial impact on macrodef/. The changes to macrodef are not Backward Compatible with the current implementation. The local task declares properties that only exist for the current scope, where scope is a target, or a sequential (any taskcontainer) or a macro instance. The patch is in http://issues.apache.org/bugzilla/show_bug.cgi?id=23942 Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
