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 12368] - [PATCH] New <subant> task to execute sub-builds
Date Fri, 06 Sep 2002 18:57:47 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=12368>.
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=12368

[PATCH] New <subant> task to execute sub-builds





------- Additional Comments From ddevienne@lgc.com  2002-09-06 18:57 -------
Steve, these are the defaults of the <subant> task, so stuff's not inherited by 
default. As far as not replicating <ant>'s mistake... All I'm doing is 
internally creating an <ant> task, so I'm limited by it. My knowledge of Ant's 
code, and the time I'm willing to invest on this, prevents me from removing 
these mistakes. 

    private String target = null;
    private String antfile = "build.xml";
    private boolean inheritAll = false;
    private boolean inheritRefs = false;
    private boolean failOnError = true;

I forgot to mention that directories in the build path get appended with the 
default ant file name, and that actual files are assumed to be Ant build files.

Regarding Nicola Ken's post, I'm not too sure how to make the connection with 
the Gump decriptors, because sub-ant deals with local build file, whereas the 
Gump descriptors describe a project generically, and one would need the 
workspace definition to know which projects are there, etc... I was thinking I 
could have a 'depends' attribute on the <project> root element of build files, 
and pre-read all the build files passed to me (getting there names, and local 
project dependencies), and infer the build order from that. In my mind, 
<subant> is for projects which belong together (like in the same CVS module), 
whereas Gump deals with disconnected projects building on each other. The 
distinction is fine, but the former could be found relative to each other 
(usually just ../dependency, like in Myrmidon or my own stuff), whereas the 
latter are more disconnected code bases. Thanks my current thinking at least.

<subant> scratch my itch, and right now I don't need more functionality that 
I've got ;-) --DD

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