Apache OpenOffice (AOO) Bugzilla – Issue 36335
Add Java Xalan 2.6 to the Office for XSL transformation
Last modified: 2004-11-29 15:37:00 UTC
Adding three JARs (xalan.jar, xercesImpl.jar, xml-apis.jar) of the Xalan distribution and adding Java calling parameter '-Xbootclasspath/p:', to assure that they will be used even a JRE/JDK 1.4 with older Xalan is install.
Added the dependency to a release engineer task. Further deliberations: Xalan is not only needed to be integrated to the Office, but for potential regression testing during build time as well. The Java startup parameter '-Xbootclasspath/p:' will not be used, as it can not be evaluated how exisiting and future Java implementations will react, as it is not even specified to be keept for SUN's Java.
What has been done: New modul Xalan has been added to build environment, and hosted by Collab. The task for module alias, necessary before the CWS will be integrated has been fixed (the cmp. 36351). A build dependency to the filter project has been added (via build.lst). The module contains three JARs (xalan.jar, xercesImpl.jar, xml-apis.jar), which will be copied during delivery to solver and integrated in program/classes. As javarc/ini is removed, the using component XSLTFilter.jar has a changed manifest entry, which loads the three jars on demand of the component (i.e. 'Class-Path: xalan.jar xercesImp.jar xml-apis.jar').
fixed
Although it is flagged as 'DEFECT' a feature mail will follow and a discussion about removing the old JAVA XSLT parser / processor will be started before integration.
reopen to exchange owner
SUS->OC: Reassign to you as JSI may not test in time.
reset to fixed
verified in internal build cws_xsltfilter04
closed because fix available in OOo1.9m63