On Jan 31, 2008, at 12:49, Vincent Hennebert wrote:
(Noticed this fragment in an earlier post, and just wanted to point
out that...)
snip /
Note that by removing the 4 aforementioned jars and using a 1.5 jdk
I have unresolved import errors in the
org.apache.fop.layoutengine.EvalCheck class.
On 31.01.2008 12:49:57 Vincent Hennebert wrote:
Hi Jeremias,
Jeremias Maerki wrote:
Vincent's feedback reminded me about something else we probably should
look at. Vincent proposed to add a dependency on the Xerces/Xalan XML
serializer. As noted, I'd prefer to stick to plain JAXP. But
I guess I don't completely understand why it's better to move away
from the status quo (if it's not broken don't 'fix' it) and increase
(IMHO) complexity.
IMO it's not enough to say 'it'll make better, more knowledgeable FOP
users' (to paraphrase ;-). I'd need measurable--or at least--obvious
Thanks Jeremias.
There are two different aspects I think:
- we used to provide JAXP for the convenience of Java 1.3 users. Now
that we have moved to Java 1.4 there is no reason anymore to provide
it. As Andreas said, buggy implementations bundled with early versions
of Java 1.4 or 1.5 is
Thanks Jeremias.
There are two different aspects I think:
- we used to provide JAXP for the convenience of Java 1.3 users. Now
that we have moved to Java 1.4 there is no reason anymore to provide
it. As Andreas said, buggy implementations bundled with early versions
of Java 1.4 or 1.5 is not
On Jan 31, 2008, at 16:25, Vincent Hennebert wrote:
snip /
Which means for today that we remove the no longer necessary
serializer.jar and xercesImpl.jar and we keep the other ones.
Solution 1, amended.
I hope I’m clear.
WDYT?
This also sounds good enough for me. As long as we can't safely
Can you two please explain to me what you mean by that?
On 31.01.2008 21:37:42 J.Pietschmann wrote:
Andreas Delmelle wrote:
Then again, since Xalan is actually needed because of the dependency on
Batik, I'm wondering whether those libraries can be moved into Commons.
Not as a mandatory
Jeremias Maerki wrote:
That means that as long as we have Batik as a mandatory dependency [1]
on our core we also have a dependency on DOM Level 3 and Xalan-J which
means we cannot remove any of the 4 JARs, except xerces.jar probably
which doesn't really have a big effect in itself. Hehe. We're
Vincent's feedback reminded me about something else we probably should
look at. Vincent proposed to add a dependency on the Xerces/Xalan XML
serializer. As noted, I'd prefer to stick to plain JAXP. But yes, with
Java 1.4 JAXP is built in so the 4 XML JARs are actually not necessary
anymore (would
On Jan 30, 2008, at 14:46, Jeremias Maerki wrote:
Vincent's feedback reminded me about something else we probably should
look at. Vincent proposed to add a dependency on the Xerces/Xalan XML
serializer. As noted, I'd prefer to stick to plain JAXP. But yes, with
Java 1.4 JAXP is built in so the
Jeremias Maerki wrote:
- Our test code has a (useful) dependency on Xalan's XPath API. Java 1.4
provides an old JAXP version without XPath support (javax.xml.xpath,
available with Java 1.5). So we've got a problem here for the time being.
Although it is valuable that users can run the test
Interesting. Both Jörg and you prefer solution 1. That's perfectly fine
with me. So if there are no other voices in the next couple of days I
shall do the necessary changes next week. It's probably best to dedicate
a separate page on the release docs to the topic so it's visible enough.
Thanks
12 matches
Mail list logo
