Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
Message-ID: <009c01c13ada$2cb44de0$5614000a@GILAMONSTER>
From: "Erik Hatcher" <jakarta-ant@ehatchersolutions.com>
To: <ant-dev@jakarta.apache.org>
References: <031501c13ac4$d7267f70$3f04a8c0@win.xtramind.dfki.de>
 <025c01c13ac7$fa8c82e0$6501a8c0@GILAMONSTER>
 <033201c13ac8$734d4ac0$3f04a8c0@win.xtramind.dfki.de>
Subject: Re: JUnit writes properties for each testcase
Date: Tue, 11 Sep 2001 08:55:26 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Thats a fairly involved modification, as the merge is independent of the
actual tests and results gathering.  Care would have to be taken (and I'm
not sure how this would be done) to ensure that the properties were matched
to the tests appropriately.

I know Stephane has some thoughts on refactoring how the JUnit tasks work,
so perhaps its time for us to start down that path and figure out a better
way for it to work.

    Erik

----- Original Message -----
From: "Ingmar Stein" <stein@xtramind.com>
To: <ant-dev@jakarta.apache.org>
Sent: Tuesday, September 11, 2001 6:48 AM
Subject: Re: JUnit writes properties for each testcase


> > How do you propose a solution?   Would an option to turn off property
> > gathering altogether be acceptable?   It would not really make sense to
> only
> > gather the properties once, so I'd think an on/off switch would be the
> best
> > way to handle it.
>
> No, I need the properties...
> A singe file that is merged with the junitreport task would suffice...
>
> Ingmar
>
>