gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Lenz <cml...@gmx.de>
Subject Re: [cactus] build failure - need help
Date Sun, 08 Jun 2003 20:36:15 GMT
A cleaner and more flexible approach might be to use an Ant XmlLogger, 
and then transform the resulting xml log file to multiple html log 
files, one for INFO, one for WARN and one for DEBUG (for example).

But, no, I'm not volunteering (yet)

Adam Jack wrote:
> This is another example of why it'd be nice to be able to set debug on in
> the gump descriptor, and have -debug passed to ant. Some build problems can
> be such that they work locally, but fail at the remote site. They need to be
> debugged at the remote site, IMHO.
> 
> I've said it before, but I'll submit an enhancement request for it this
> time.
> 
> regards
> 
> Adam
> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@pivolis.com]
> Sent: Friday, June 06, 2003 3:09 PM
> To: gump@jakarta.apache.org
> Subject: [cactus] build failure - need help
> 
> 
> Hi,
> 
> I need some help to diagnosis why the jakarta-cactus-sample-servlet-12
> project is failing to build with Gump. The problem has to do with
> starting Tomcat 3.x but the build output is not enough to diagnosis the
> problem.
> 
> During the build there is a file created:
> jakarta-cactus/samples/servlet/target-12/test/test-reports/tomcat3x.out
> 
> Would it be possible to have access to this file?
> 
> More generally is there a way to a web read access to the area where
> Gump builds the projects on Nagoya?
> 
> Thanks
> -Vincent

-- 
Christopher Lenz
/=/ cmlenz at gmx.de


Mime
View raw message