Return-Path: 
 <ant-user-return-17512-qmlist-jakarta-archive-ant-user=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@apache.org
Received: (qmail 89070 invoked from network); 15 Feb 2002 13:52:24 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 15 Feb 2002 13:52:24 -0000
Received: (qmail 14984 invoked by uid 97); 15 Feb 2002 13:52:17 -0000
Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org
Received: (qmail 14950 invoked by uid 97); 15 Feb 2002 13:52:16 -0000
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-user-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-user-help@jakarta.apache.org>
List-Post: <mailto:ant-user@jakarta.apache.org>
List-Id: "Ant Users List" <ant-user.jakarta.apache.org>
Reply-To: "Ant Users List" <ant-user@jakarta.apache.org>
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 5333 invoked from network); 15 Feb 2002 13:45:24 -0000
Message-Id: <200202151345.g1FDjHh32727@loki.exolution.lan>
X-Authentication-Warning: loki.exolution.lan: monsorno set sender to
 monsorno@gmx.de using -f
To: "Ant Users List" <ant-user@jakarta.apache.org>
Subject: Re: How to warn when jar-file in classpath does not exist?
References: <200202141323.g1EDNb019470@loki.exolution.lan>
	<034f01c1b59b$2e7480f0$b81c570f@cv.hp.com>
From: Martin Monsorno <monsorno@gmx.de>
Date: Fri, 15 Feb 2002 14:45:17 +0100
In-Reply-To: <034f01c1b59b$2e7480f0$b81c570f@cv.hp.com> ("Steve Loughran"'s
 message of "Thu, 14 Feb 2002 13:04:18 -0800")
Lines: 15
User-Agent: Gnus/5.090006 (Oort Gnus v0.06) XEmacs/21.4 (Artificial
 Intelligence, i386-suse-linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

"Steve Loughran" <steve_l@iseran.com> writes:

> standard practise is to use <available> to probe for a class you
> need; that decouples you from knowing where the class is
> implemented, then conditional <fail> if you really need that class
> to be there

Yes, but available is _very_ inconvenient, because you always define
two more targets: one that contains the available-task, and one that
is called depending on the available-set-property that does the
appropriate things.

-- 
Martin Monsorno
mailto:monsorno@gmx.de

--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>