DO NOT REPLY [Bug 27936] - fop jars conflict with newer versions

[bu...@apache.org]

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=27936>.
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=27936

fop jars conflict with newer versions

glenmazza@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From glenmazza@yahoo.com  2004-03-25 05:32 -------
In the long run, you will be better off using Apache Ant and storing your
classpaths there, rather than on the system CLASSPATH.  Learning Ant is time
*extremely* well spent--I never bother with the CLASSPATH anymore.

Anyway, we've noticed the problem before, but we will not be changing 0.20.5
(I'm unsure if there is anything we could change anyway)--please use the xml
libraries supplied in the lib directory.

fop.sh specifically activates (using Apache Ant, no less) the xml libraries in
the fop/lib directory, which are the JARs that have been tested with FOP.  There
are tons of versions of Xalan/Xerces that will work and tons that won't work
with FOP--there's nothing we can do about it--our code is "legal".

Indeed, even though V1.4+ of the JDK already includes Xalan and Xerces, many
applications must still specifically supply a different version, because the Sun
versions won't work with what they have.