Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 61643 invoked from network); 2 Apr 2004 14:58:34 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Apr 2004 14:58:34 -0000 Received: (qmail 91009 invoked by uid 500); 2 Apr 2004 14:58:27 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 90969 invoked by uid 500); 2 Apr 2004 14:58:27 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 90954 invoked from network); 2 Apr 2004 14:58:27 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 2 Apr 2004 14:58:27 -0000 Received: (qmail 23670 invoked by uid 50); 2 Apr 2004 14:59:08 -0000 Date: 2 Apr 2004 14:59:08 -0000 Message-ID: <20040402145908.23669.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@ant.apache.org Cc: Subject: DO NOT REPLY [Bug 28127] - documentation does not describe effects on target dependencies X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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 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