Return-Path: 
 <dev-return-49856-apmail-ant-dev-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 55485 invoked by uid 500); 22 Aug 2003 16:30:51 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@ant.apache.org>
List-Subscribe: <mailto:dev-subscribe@ant.apache.org>
List-Help: <mailto:dev-help@ant.apache.org>
List-Post: <mailto:dev@ant.apache.org>
List-Id: "Ant Developers List" <dev.ant.apache.org>
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 50415 invoked by uid 500); 22 Aug 2003 14:10:01 -0000
Message-ID: <ECE60FFBB1DDBF4DA10DA1C93843A4B702FD2FCC@freeport.synygy.com>
From: "Inger, Matthew" <inger@Synygy.com>
To: "'ant-dev@jakarta.apache.org'" <ant-dev@jakarta.apache.org>
Subject: Condition as a top level element
Date: Fri, 22 Aug 2003 10:09:54 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C368B7.0F4E27F0"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

------_=_NextPart_001_01C368B7.0F4E27F0
Content-Type: text/plain;
	charset="iso-8859-1"

Is it possible in the future to make <condition> a top level element?
It's essentially the same idea as <property>, but with restrictions.
The basic reason is that i'd like to have something like this at the
top of my project:

<condition property="script.extension" value=".sh">
   <os family="unix" />
</condition>

<condition property="script.extension" value=".bat">
   <os family="windows" />
</condition>


So that I don't have to muddy up the depend structure in
order for a target to know what extension to use for a script
file on the current os.

Thoughts?

----------------
Matthew Inger [inger@synygy.com]
Software Developer
Synygy, Inc
610-664-7433 x 7770
"Man who jump off cliff, leap to conclusions." - Confucious


------_=_NextPart_001_01C368B7.0F4E27F0--