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 28127] - <parallel> documentation does not describe effects on target dependencies
Date Fri, 02 Apr 2004 14:59:08 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28127>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28127

<parallel> documentation does not describe effects on target dependencies





------- Additional Comments From gudnabrsam@yahoo.com  2004-04-02 14:59 -------
Maybe this is just a matter of interpretation, but I can't think of a situation 
in which you would want a target that would normally be executed sequentially, 
but when used from certain antcalls would be executed in parallel.  What if I 
had a target that first compiled, then linked, some programs?  If someone else 
imported my targets, then invoked one via antcall with cascading parallel 
execution, all of a sudden I'm trying to link files that may not be finished 
compiling yet, and who are they going to come asking why it doesn't work?  
Maybe not me, but maybe so... we could, I suppose, add something to the doc 
informing the user not to expect this, but my feeling is "if we never mentioned 
it, why would they expect it?"

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


Mime
View raw message