ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Burton <>
Subject Re: Fop Task
Date Tue, 07 Jan 2003 17:41:38 GMT

Christopher Lenz wrote:

> BTW, the <fop> Task is *extremely* noisy with debugging/warning/error 
> output (as is the commandline), and I haven't figured out a good way to 
> turn the volume down with the Ant task.

An adapter to Ant's logger should be written.  By specifying the various 
logging level options to Ant, -quiet, nothing, -verbose and -debug, this 
would also control the logging verbosity of the FOP output.  It also 
means the FOP output goes to the same place as Ant's log.

I wrote such a logging adapter for DVSL that routes all Velocity 
messages through Ant's logger.  It's very simple and could probably be 
adapted for FOP provided it has some logging abstraction.

It's documented at

You can see it at


> Jerome Paul wrote:
>> Would it be possible to have examply code showing how to access the 
>> fop task
>> sent to the list.
>> cheers
>> Jerome
>> -----Original Message-----
>> From: Joerg Pietschmann []
>> Sent: Tuesday, 7 January 2003 5:23 AM
>> To: Ant Users List; Stefan Bodewig
>> Subject: Re: Fop Task
>> On Monday 06 January 2003 09:37, Stefan Bodewig wrote:
>>> Should we point to it from our external tasks section?  I almost think
>>> it shouldn't be necessary as people who want a FOP task will have the
>>> FOP distribution already and will know about the task from FOP's docs.
>> Ahem: it's completely undocumented and well hidden. Someone ought
>> to do something about this. Well, I guess this someone will be me...
>>> Does it get compiled by the nightly Gump runs?
>> I'd say yes, but I wouldn't back this if asked officially.
>> J.Pietschmann

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message