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 3757] - <include> task to include external XML files containing Ant definitions
Date Sat, 22 Sep 2001 06:22:21 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=3757>.
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=3757

<include> task to include external XML files containing Ant definitions

steve_l@iseran.com changed:

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



------- Additional Comments From steve_l@iseran.com  2001-09-21 23:22 -------
Ovidiu,

An include mechanism is one of the requirements for Ant 2.0: "Ant2 will 
provide a built-in include mechanism.", as it says under the extensibility 
section, glossing over the subtleties of what it will be, how it will work, 
etc.

Till then, you can use the traditional method of including XML files into 
another XML file, something delegated to the parser. That's a primitive yet 
viable way of sharing definitions between projects. Properties can be shared 
with property files, and there is always the <ant> task to call a target in 
another file. Note also that you can feed back results from an <ant> call into 
a parent build by writing them to a properties file and loading it in the 
parent. At that point your build is probably starting to look pretty hairy 
though, so I don't recommend that approach.

Mime
View raw message