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 11836] New: - Support for properties in Targets
Date Mon, 19 Aug 2002 22:20:09 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=11836>.
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=11836

Support for properties in Targets

           Summary: Support for properties in Targets
           Product: Ant
           Version: 1.5
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: rfeak@cox.net


Currently properties are not usable in the attributes of targets.

I have recently run into a situation where this would be useful. I have to set 
up a build system where there are multiple sub-components. Each one should be 
buildable and testable within itself. In addition I have to have a master build 
file that will build and test everything. This is totally doable. However, I do 
not want to "own" the build system, so the easier I can make it the better.

One thing I want to do is have a common set of targets for each component so 
that the master build can assume what targets are available. Also, I would like 
to make a utilities.xml file that has those targets in them. In the simplest 
case (no dependancies, nothing special) the individual components could just 
source the utilities.xml. In more complex cases, I would like the components to 
be able to source the utilities.xml also, but be able to set additional 
dependancies for some of the compile targets. Those additional dependancies 
could then be placed in that components build.xml.

A system like this is a little complex to setup initially, but not too bad. 
Easy to add new components to in the long run, and minimizes the amount of code 
that gets copy and pasted.

Unfortunately I cannot create a property that describes what dependancies exist 
for a particular target. It seems like this should be an easy thing to add, if 
you deem it worthy.

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