Return-Path: Delivered-To: apmail-ant-user-archive@www.apache.org Received: (qmail 71039 invoked from network); 18 Jan 2010 12:11:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Jan 2010 12:11:29 -0000 Received: (qmail 3640 invoked by uid 500); 18 Jan 2010 12:11:28 -0000 Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 3565 invoked by uid 500); 18 Jan 2010 12:11:28 -0000 Mailing-List: contact user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list user@ant.apache.org Received: (qmail 3555 invoked by uid 99); 18 Jan 2010 12:11:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jan 2010 12:11:28 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [62.154.176.138] (HELO icon040.icongmbh.de) (62.154.176.138) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jan 2010 12:11:21 +0000 Received: from icsrv02.icongmbh.de (unknown [192.168.195.2]) by icon040.icongmbh.de (Postfix) with ESMTP id C1DB411536 for ; Mon, 18 Jan 2010 13:10:47 +0100 (CET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: AW: ant log/output vs. unless/if on a target Date: Mon, 18 Jan 2010 13:10:47 +0100 Message-ID: <06080D44730F41428BAF2168FA8BDD800437A290@icsrv02.icongmbh.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ant log/output vs. unless/if on a target Thread-Index: AcqYMi5inynlBsHaQLKIWOY4+Zx2KAABEIyw References: <6CDC32AFFBA5AA4B8BEA6397594F76BD20151548F2@han-hb-exch-002.brox.de> From: "Knuplesch, Juergen" To: "Ant Users List" Hello, The workaround is to use antconribs task to do what "if/unless" = does. Greetings Juergen --=20 J=FCrgen=20 -----Urspr=FCngliche Nachricht----- Von: Thomas Menzel [mailto:tmenzel@brox.de]=20 Gesendet: Montag, 18. Januar 2010 12:34 An: user@ant.apache.org Betreff: ant log/output vs. unless/if on a target Hi, Maybe I just don't know enough and this already works, but it would be = really great if ant would tell by default that a target isn't executed = because of an if/unless. I just stumbled over this when I wanted to turn a target off that I'm = calling with and was wondering and debugging why the target = was still executed since it showed up in the log. (the target produces = no log-output itself). I first had the idea that mentioning of the target should be suppressed = completely but I 2nd that thought since it is good to know the = dependency graph, so I'm settling for a hint that the target isn't = executed. Suggestions: : (target skipped) // this is the normal version : (skipped due to [if failed] [unless succeeded]) // this = is the verbose version Any opinions on that? --- tom --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional = commands, e-mail: user-help@ant.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org