+1 to that And while we're here, is there any way to switch OFF SVG support so the batik jar is dispensible? I'm using fop as the printing API for a desktop/Swing app and it is brilliant (proper print preview, high quality saved and printed documents, easy format to build with) but the size of the jars is quite a big issue: it's about 80% of the size of the application right now! More jars are not needed.
Al ps - I log in a pretty crude way (debug, info, warn, error) to a class which ATTEMPTS to load log4j and use that: but if it can't, or if it's called on a thread before log4j has initialised properly, it just writes to stdout. -----Original Message----- From: Joe Batt [mailto:[EMAIL PROTECTED]] Sent: Friday, August 03, 2001 4:13 PM To: [EMAIL PROTECTED] Subject: Re: logging When FOP is a production ready library, I wont care for any FOP logging. Logging in FOP now is only for debugging as far as I'm concerned. There is no need for integration into other logging systems. Think about how you use other libraries. Joe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
