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 28447] New: - Add an "private" attribute to targets
Date Sat, 17 Apr 2004 02:42:48 GMT
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=28447>.
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=28447

Add an "private" attribute to targets

           Summary: Add an "private" attribute to targets
           Product: Ant
           Version: 1.6.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core
        AssignedTo: dev@ant.apache.org
        ReportedBy: mharrah@dollartree.com


Sometimes we have targets that are really only useful as a "subroutine" sort 
of thing.  For example, we might have target A that depends on target B, and 
has an unless attribute for property Foo.  Target B consists of an uptodate 
check and sets property Foo if things are up-to-date.  It makes no sense to 
call target B from the command line.

It would be nice if there were an optional attribute on targets that would 
allow you to mark a target as "for internal use only" and would not show up in 
ant -projecthelp (even if a description were specified), and would cause an 
error if called from the command line.

This would also make it easier when generating documentation from build 
scripts to know "public" or "main" targets from the subroutine type targets.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message