ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18324] New: - Global Tasks
Date Tue, 25 Mar 2003 15:50:08 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18324>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18324

Global Tasks

           Summary: Global Tasks
           Product: Ant
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Optional Tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: andre.malenfant@cgi.com


It would be a great improvement to be able to create custom tasks that CAN be 
called globally, i.e. not forced to be used inside a target. Like the property 
task or the path type.

In our case, it leads to weird patterns because we have to create useless 
target and add dependencies everywhere to be able to have cutom global 
initialization sections.

I looked in ant's source code and it is hardcoded that only property, taskdef, 
target and path be recognized outside of a target. You could create a new 
interface that, when implemented, permits the use of those tasks globally.

Mime
View raw message