DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40511>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40511

           Summary: Add compenentdef to ant
           Product: Ant
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Core
        AssignedTo: dev@ant.apache.org
        ReportedBy: [EMAIL PROTECTED]


This proposal is to add a new type definition to ant.

The def task is <componentdef>.

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 ambiguous. 

The patch modifies IH and co. to lookup nested-element in tasks/types
that have add(X)-type methods, in a new mapping called restricted
types (because they cannot use by themselves, only as nested element of
declared tasks/types).

Useage: in a antlib.xml or build.xml file:

<componentdef name="add"
   classname="org.apache.tools.ant.taskdefs.condition.Add"/>

<componentdef name="add"
   classname="org.apache.tools.ant.types.selectors.AddSelector"/>

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to