DO NOT REPLY [Bug 41044] - [PATCH] FOP memory usage patches.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: New releases

On Dec 16, 2006, at 20:17, Vincent Hennebert wrote: For Fop 0.93 we will have to define what needs to be absolutely done before releasing. I'm personally in favor of releasing as is because we can't wait more. It would be great to release before Christmas but that'll be tight IMO... IMO

[EMAIL PROTECTED]: Project xml-fop (in module xml-fop) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop has an issue affecting its community integration. This issue affects 1 pr

[EMAIL PROTECTED]: Project xml-fop (in module xml-fop) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop has an issue affecting its community integration. This issue affects 1 pr

Re: New releases

On Sun, Dec 17, 2006 at 01:14:40PM +0100, Andreas L Delmelle wrote: > IMO, if we want to mark this FOP-release as production-ready, we > might want to have a look at incorporating some of Richard Wheeldon's > ideas (see Bugzilla 41044 and 41009), mainly the selective commenting > out of unuse

Bug report for Fop [2006/12/17]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned