From ant-user-return-10909-apmail-jakarta-ant-user-archive=jakarta.apache.org@jakarta.apache.org Wed Aug 01 14:53:25 2001
Return-Path:
Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org
Received: (qmail 36642 invoked by uid 500); 1 Aug 2001 14:53:24 -0000
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Post:
List-Help:
List-Unsubscribe:
List-Subscribe:
Reply-To: ant-user@jakarta.apache.org
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 36631 invoked from network); 1 Aug 2001 14:53:20 -0000
From: =?us-ascii?Q?Jerome_Lacoste?=
To:
Subject: RE: JUnit output (System.out) not printed.
Date: Wed, 1 Aug 2001 16:50:19 +0200
Message-ID:
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
In-Reply-To:
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N
> > I upgraded to Ant 1.4 nightly and I found out that the JUnit output
> > (System.out, System.err) is not printed anymore.
>
> Your use-case indicates that we don't cover everything with this, maybe
> we should decouple the handling of System.out/.err from the summary
> formatter and add another attribute that indicates whether we want to
> swallow System.err/.out (i.e. hand it to the formatters exclusively,
> we currently do) or let output go to the original streams as well
> (unbuffered).
>
> What do you think?
Sory for the delay, I was away for a while.
As I said in my initial email I need user interaction through in my tests.
Otherwise I loose interest in running my Unit Tests in Ant.
Adding the attribute seems a good idea. I don't think of anything else as
easy that could provide the same functionality and flexibility.
I unfortunately don't have time to provide a fix. But perhaps should I
create a bug report?
One important point is that as I mentioned, some of my output gets Printed!
This output is handled by a logging class whose instance has a PrintStream
field initialised to System.out.
To summarize the System.err/out outputs inside my JUnit classes are not
printed, but some of the debugging output code contained in my library being
tested gets printed...
Might there also be a bug?
Jerome