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 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 sending the Batik team a little patch for their build.xml so we get
an Ant target for creating a big batik.jar like we need/like it for FOP.
You'll hear from me again.
On 19.01.2003 12:05:53 Oleg Tkachenko wrote:
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 of it, but
when he replaces batik.jar for a bunch of batik jars except of batik-ext.jar
it works ok.
Anybody has any ideas?
Jeremias Maerki
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
