Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Date: Mon, 3 Jan 2005 19:32:56 +0100
Message-Id: <200501031832.j03IWug2002309@ajax.apache.org>
From: bugzilla@apache.org
To: dev@ant.apache.org
Subject: DO NOT REPLY [Bug 22901]  -
    [Patch] -only option to execute target(s) without dependencies

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=22901>.
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=22901


------- Additional Comments From gudnabrsam@yahoo.com  2005-01-03 19:32 -------
A big problem here, again, is the fact the sensible way to process multiple
targets specified via nested elements on a single ant(call) invocation is with
single-check execution; otherwise multiple tasks could be used.  Ordinarily,
then, you have default target execution for the main Project and single-check
execution for ant(call)-based Project instances.  The parallel case and its
threadcount limitations is a good one; executor inheritance would definitely be
useful here, but we end up with this conflict.  At this point the only
compromise I see is to inherit the executor, with the rule being that nested
targets will cause a single-check executor to be used in place of a default
executor; or a new keep-going/single-check executor to be used in place of a
keep-going executor; but no other combination of circumstances will result in
such a substitution.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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