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 8084] - Need access to current target name
Date Tue, 16 Apr 2002 01:25:03 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=8084>.
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=8084

Need access to current target name

greno@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |



------- Additional Comments From greno@yahoo.com  2002-04-16 01:25 -------
from reporter:

Steve,
   I can easily do the type of things that I'm requesting for ant with make.  I 
would at least expect as much flexibility with ant.  Your last suggestion is 
exactly what I'm doing now and it's far too messy.  If you add a target to a 
sub build then you have to move up the heirarchy and place it in the higher 
level build file also.  I also need to be able to have all targets go through a 
catchall type target.  We need to be able to do this list/pattern matching 
thing.  In make I can use things like '$$@' to reference the current target.  I 
should be able to do a similar thing with ant.  I can also wildcard match 
targets.  I can also have targets go through multiple target stanzas.  I don't 
buy the 'wild scripting things' argument.  We've been doing this type of thing 
with make for eons without any problem.
   I ask that you reconsider this request.

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


Mime
View raw message