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 28445] - add description attribute to project and macrodefs
Date Mon, 19 Apr 2004 13:33:38 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=28445>.
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=28445

add description attribute to project and macrodefs





------- Additional Comments From mharrah@dollartree.com  2004-04-19 13:33 -------
Taskname would not be suitable for our use as a description (although it could 
be for other people), primarily because it gets emitted to your listeners as 
the task runs, and it overrides what the actual task is.

We use taskname to give a better indication to the listeners what's really 
being done.  For example, if we are using a <java> task to run ejbc, we put 
taskname="ejbc" in the <java> task so when the script is running, instead of 
[java] being shown to stdout, we see [ejbc].

Besides, most tasks have a description attribute on them, so we use that for 
descriptions.   I am just curious why it isn't on ALL ant-supplied tasks, and 
on other constructs as well.

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


Mime
View raw message