You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Oleg Tkachenko <ol...@multiconn.com> on 2003/01/19 12:05:53 UTC
duplicated sax classes
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 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?
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: duplicated sax classes
Posted by Oleg Tkachenko <ol...@multiconn.com>.
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.
Great, thanks!
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: duplicated sax classes
Posted by Oleg Tkachenko <ol...@multiconn.com>.
Keiron Liddle wrote:
> 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.
Fine. I would be nice to have such batik.jar in 0.20.5 release.
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: duplicated sax classes
Posted by Keiron Liddle <ke...@aftexsw.com>.
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: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: duplicated sax classes
Posted by Jeremias Maerki <de...@greenmail.ch>.
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: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org