DO NOT REPLY [Bug 36815] java.lang.NoSuchMethodError when working together with batik 1.6
https://issues.apache.org/bugzilla/show_bug.cgi?id=36815 Glenn Adams gl...@skynav.com changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #3 from Glenn Adams gl...@skynav.com 2012-04-01 13:53:59 UTC --- batch transition to closed remaining pre-FOP1.0 resolved bugs -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 36815] - java.lang.NoSuchMethodError when working together with batik 1.6
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36815. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36815 --- Additional Comments From [EMAIL PROTECTED] 2005-10-02 01:04 --- Batik 1.6 is not compatible with FOP 0.20.5. FOP 0.20.5 will only run with the Batik release also included in the FOP distribution. This is a documented restriction. A better resolution of the bug would be INVALID. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 36815] - java.lang.NoSuchMethodError when working together with batik 1.6
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36815. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36815 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2005-09-26 18:26 --- It may be a known issue, I can't say for sure. What I CAN say for sure, is that, since this relates to version 0.20.5, this won't be fixed --either use the Batik Version supplied with FOP 0.20.5, or better, try out FOP's svn-trunk, which does work with Batik 1.6. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Re: DO NOT REPLY [Bug 36815] - java.lang.NoSuchMethodError when working together with batik 1.6
On Sep 26, 2005, at 18:26, [EMAIL PROTECTED] wrote: snip / [EMAIL PROTECTED] changed: What|Removed |Added --- - Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2005-09-26 18:26 --- It may be a known issue, I can't say for sure. What I CAN say for sure, is that, since this relates to version 0.20.5, this won't be fixed BTW: Everyone agreed that, since version 0.20.5 will quite soon be outdated, it may be time to start cleaning out the bug-list? (Not that it matters that much. Just yesterday, I saw someone CC-ing himself for a bug that had been marked 'RESOLVED INVALID' ages ago :-) Some people...) If so, what would be the best strategy: - simply mark all bugs related to 0.20.X as WONTFIX, with maybe a tiny message that the new pre-release is pending --encourages users to try out the trunk, and create new bug-reports if they encounter the same problem - check if current trunk version still has the bug, and if it has, change the version --more work for us, I guess :-( Cheers, Andreas
Re: DO NOT REPLY [Bug 36815] - java.lang.NoSuchMethodError when working together with batik 1.6
On Tue, 27 Sep 2005 01:23 am, Andreas L Delmelle wrote: On Sep 26, 2005, at 18:26, [EMAIL PROTECTED] wrote: snip/ BTW: Everyone agreed that, since version 0.20.5 will quite soon be outdated, it may be time to start cleaning out the bug-list? (Not that it matters that much. Just yesterday, I saw someone CC-ing himself for a bug that had been marked 'RESOLVED INVALID' ages ago :-) Some people...) If so, what would be the best strategy: - simply mark all bugs related to 0.20.X as WONTFIX, with maybe a tiny message that the new pre-release is pending --encourages users to try out the trunk, and create new bug-reports if they encounter the same problem - check if current trunk version still has the bug, and if it has, change the version --more work for us, I guess :-( I think it has to be the :-( strategy one. Cheers, Andreas Manuel
