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 Mon, 15 Apr 2002 17:25:43 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

steve_l@iseran.com changed:

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



------- Additional Comments From steve_l@iseran.com  2002-04-15 17:25 -------
I see what you are getting at, and dont think it will go in.

1. The notion of a magic property which has the current name in it has been 
proposed and rejected in the past, primarily because it lets you do wild 
scripting things

2. your idea of wildcarded implementation of target names is interesting, but 
also not on the cards. Without a target name property it isnt going to be much 
use anyway.

It looks like you are trying to pass targets down to a sub project, true?

1. have a target for each build file which calls that sub project with a 
target set as a parameter

2. set the dependencies of these 'proxy' targets up to match build file 
dependencies

3. have entry point targets 'release' 'deploy' which call the final proxy 
target, probably with an <antcall>

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