Return-Path: 
 <ant-dev-return-20308-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@apache.org
Received: (qmail 79768 invoked from network); 27 Nov 2001 12:40:27 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 27 Nov 2001 12:40:27 -0000
Received: (qmail 3285 invoked by uid 97); 27 Nov 2001 12:40:23 -0000
Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org
Received: (qmail 3268 invoked by uid 97); 27 Nov 2001 12:40:22 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-dev-help@jakarta.apache.org>
List-Post: <mailto:ant-dev@jakarta.apache.org>
List-Id: "Ant Developers List" <ant-dev.jakarta.apache.org>
Reply-To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 3257 invoked from network); 27 Nov 2001 12:40:22 -0000
Message-ID: <002901c17740$ab23b1a0$6401a8c0@darden.virginia.edu>
From: "Erik Hatcher" <jakarta-ant@ehatchersolutions.com>
To: "Ant Developers List" <ant-dev@jakarta.apache.org>
References: <00d801c175ba$0d82b040$6401a8c0@darden.virginia.edu>
 <200111270741.fAR7f8J29510@mail004.syd.optusnet.com.au>
 <00dc01c17731$6e7e0520$6401a8c0@darden.virginia.edu>
 <200111271103.fARB3mJ26866@mail004.syd.optusnet.com.au>
Subject: Re: <available> / <condition> breaking immutability
Date: Tue, 27 Nov 2001 07:40:16 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

----- Original Message -----
From: "Peter Donald" <peter@apache.org>
> > Ok.  I suspect some folks might rely on the behavior of <junit>, run a
> > series of tests and put them all to the same error or failure property,
> > then do something based on the value of that property.  The way to get
> > around that would be to have them all go to separate properties, then do
a
> > <condition> on them all to set a single property.
>
> Okay - can junit store this result in different propertys? If so then lets
> document it and document alternative approach (ie using condition) and
THEN
> issue an annoying warning ;)

Yes, <junit> has both errorProperty and failureProperty attributes that
allow the user to define the property names to get set.




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