I don't think there's a patch around for that. If you think making AWT optional is important please file a "request for enhancement" in BugZilla for future reference so we can respect that in the redesign.
I think it should be relatively simple to make AWT optional. Basically two steps are necessary: - Modify build.xml so only the AWT-dependant classes can be compiled conditionally. - Modify the classes that have AWT-dependant stuff in them so they run without AWT (see Jimi, JAI and JCE support as an example). There are special AWT-backends out there for headless servers. Maybe there's also a dummy AWT package somewhere. Just a thought. On 18.04.2003 16:26:22 Tim Landscheidt wrote: > okay, some googling showed that the culprit is gij :-(. > > Another question in this regard: Has anybody played with > FOP and gcj? Some time ago, the AWT viewer was a problem as > gcj did not provide any Swing classes. Is there any patch > available that deletes all references to the AWT viewer? Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
