On Tue, 12 Sep 2006, Peter Reilly <[EMAIL PROTECTED]> wrote: > Ok, I dug out my old code and after digging out some of the bugs > and misunderstanding, I have modded IH, CH (componenthelper), > and <typedef> to allow "restricted" types. > > These are like normal types except: > 1) they are only allowed in add[Configured](Class) contexts, they > cannot be used at the top level or task containers. > 2) One can have a multiple number of definitions with > the same name. IH will pick the one that matches the > add() methods in the container class. If there are multiple > matches, - for example class that has add(Condition) and > add(FileSelector) > presented with "and", IH will throw a buildexception for > ambigeous.
+1 > I am not too sure this should be user visible but it can be > implemented by an extra attribute to the typedef task - > restrict=yes/no default is no. Like the others I'd prefer a new taskname as well, just don't ask me for names. > One problem is that the antlib.xml for antlib:org.apache.tools.ant > would be long and tedious when all the conditions, selectors, > mappers, resources are added. I don't think this is really that big a problem, but I'm fine with automation as well. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
