Return-Path: <bodewig@apache.org>
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 53751 invoked from network); 19 Mar 2003 07:08:09 -0000
Received: from bodewig.bost.de (195.227.98.11)
  by daedalus.apache.org with SMTP; 19 Mar 2003 07:08:09 -0000
Received: (from bodewig@localhost)
	by bodewig.bost.de (8.11.6/8.11.6) id h2J78JJ20603;
	Wed, 19 Mar 2003 08:08:19 +0100
X-Authentication-Warning: bodewig.bost.de: bodewig set sender to
 bodewig@apache.org using -f
To: user@ant.apache.org
Subject: Re: available task
References: <3E77C453.7080104@brutele.be>
From: Stefan Bodewig <bodewig@apache.org>
Date: 19 Mar 2003 08:08:19 +0100
In-Reply-To: <3E77C453.7080104@brutele.be>
Message-ID: <m34r5zq1ek.fsf@bodewig.bost.de>
Lines: 14
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Military Intelligence)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Wed, 19 Mar 2003, Thomas Lionel SMETS <tsmets@brutele.be> wrote:

> Is there a reason why we can't use the <available /> task as a
> <property/> definiton ?

The real question is "Is there a reason why we can't use the
<available /> task outside of <target>".  In 1.5.x the answer is: you
can't, but there is no real reason.

As a corollary, you will be able to do it in 1.6 (or current CVS,
latest nightly builds ...).  All tasks can be used outside of targets
in the future.

Stefan