ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Hatcher" <jakarta-...@ehatchersolutions.com>
Subject Re: <available> / <condition> breaking immutability
Date Tue, 27 Nov 2001 12:40:16 GMT
----- 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>


Mime
View raw message