Hello!
We've got SAX classes both in xml-apis.jar and batik.jar. I don't care about
superfluous 10-20 Kb, but unfortunately it causes problems in some
environments, for instance in eclipse. One fellow has developed FOP plugin for
eclipse and he's got Duplicate class definition problem because
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16237.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16237.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I think we could just remove the SAX classes from batik.jar. batik.jar
was compiled by us manually and Keiron (for trunk) and I (for branch) both
haven't realized that the SAX classes slipped in, I guess. I'll check
the way we generate that jar again tomorrow. It might simply be a matter
of
Current cvs batik has been fixed so that it uses the xml-apis.jar
instead of having its own version. So if this is what is causing the
problem you can make a build from current cvs.
On Sunday, January 19, 2003, at 06:41 PM, Jeremias Maerki wrote:
I think we could just remove the SAX classes
