Apache OpenOffice (AOO) Bugzilla – Issue 14064
New requirement for build of beta2: javax.xml.transform.Transformer
Last modified: 2003-09-06 19:33:37 UTC
Hi, do we need additional packages for building beta2 over beta1? New directories xsltvalidate and xsltfilter seems to need javax.xml.transform.TransformerFactory: pavel@oo:~/BuildDir/ooo_11beta2_src/filter/source/xsltvalidate> dmake Making dpj... javac -classpath ".:../../unxlngi4.pro/class:/usr/lib/java/jre/lib/rt.jar:.:/mnt/hdc2/pavel/BuildDir/ooo_11beta2_src/solver/644/unxlngi4.pro/bin/sandbox.jar:/mnt/hdc2/pavel/BuildDir/ooo_11beta2_src/solver/644/unxlngi4.pro/bin/ridl.jar:/mnt/hdc2/pavel/BuildDir/ooo_11beta2_src/solver/644/unxlngi4.pro/bin/unoil.jar:/mnt/hdc2/pavel/BuildDir/ooo_11beta2_src/solver/644/unxlngi4.pro/bin/jurt.jar:/mnt/hdc2/pavel/BuildDir/ooo_11beta2_src/solver/644/unxlngi4.pro/bin/juh.jar" -d ../../unxlngi4.pro/class XSLTValidate.java XSLTValidate.java:77: cannot resolve symbol symbol : class TransformerFactory location: package transform import javax.xml.transform.TransformerFactory; ^ XSLTValidate.java:78: cannot resolve symbol symbol : class Transformer location: package transform import javax.xml.transform.Transformer; ^ XSLTValidate.java:79: cannot resolve symbol symbol : class DOMSource location: package dom import javax.xml.transform.dom.DOMSource; ^ XSLTValidate.java:81: cannot resolve symbol symbol : class TransformerException location: package transform import javax.xml.transform.TransformerException; ^ ... 31 errors dmake: Error code 1, while making '../../unxlngi4.pro/misc/XSLTValidate_dummy.java' ---* TG_SLO.MK *--- If this is the case, we need a check for the new packages in config_office, I think.
Does this also mean we need new Java also for runtime? E.g. for GNU/Linux on i386 (scp/source/office/files.scp): RequiredVersion=1.4.0_02 ExcludeVersion=1.4.1 Is this for real? 1.0.3 supported 1.3.1 as well. many distributions have 1.4.1... See also http://www.openoffice.org/issues/show_bug.cgi?id=14282
For JDK 1.3.1 we need those additional packages: xalan.jar, crimson.jar and xml-apis.jar.
TM->HR: Can you please have a look ? Seems to be not a framework issue to me. Please send it to the appropiate developer if you aren´t the right one. Thanks !
HR->JL: Please comment on why jdk-1.4.1 is in the exclude list.
SUN Java 1.4.1 does not contain a fix for accessibility which went into 1.4.0_02 and 1.4.1_01. I don't know if the patch ids, suche as _01 can be compared at all with Javas of other vendors. Since we only test with SUN Java we cannot guarantee that other Javas work at all. However, the Java setup should allow to select other Javas independent of its version. But that only works if those Javas have the same directory structure, library names, executable names, etc. BTW, raising the requirement was demanded by our product management.
So should this be fixed in the code instead of generally disable 1.4.1? Ie. if accessibility is installed that particular version is not enough?
As I said, 1.4.1 does not contain a needed fix. Therefore it was excluded. Go for SUN Java 1.4.1_01 instead or use the browse button in the Java setup to select a 1.4.1. I know, the latter is not possible yet, but that was fixed and is about to go into the product.
There is no Java 1.4.1 for all platforms yet.
Therefore you can browse to the Java of your choice in the Java setup and select it. This was not possible in 1.1beta but should be fixed for the final.
I do not have anything to say here. So the summary is: 1. We need additional JAR files if 1.3.1 is used for build. -> This should be written in the Linux build guide. 2. JDK 1.4.1 is preferred Java. 3. For runtime, you need 1.4 anyway so you can not use it on e.g. PowerPC. Is it right?
1. AFAIK, there is a filter which uses XSLT. For building one needs those XML, XSLT jars, but do not know which. I will forwards this issue appropriately. 2. SUN Java 1.4.0_02, 1.4.0_03, etc. currently meet the requirement as well. Then 1.4.1_01, etc.. 3. The Java runtime (java - uno bridge, etc.) runs with 1.3.1. JL->MIB: Could you clarify what additional jars are needed to build with 1.3.1. Also, Pavel asked to put a not into the LINUX build guide. Could you take of that?
Additional jars are mentioned in one of my comment to this bug.
Aidan, can you please clarify which JDK/jars are required.
aidan: The additional packages that are required are : xalan.jar (contains javax.xml.transform.Transformer) xml-apis.jar (xml apis) and crimson.jar or xerces.jar (XML parsers) Xalan is available here: http://xml.apache.org/xalan-j/downloads.html Additional info: JAVA 1.4.0 and above contains crimson and xalan by default, hence there is no requirement for the additional jars when building with 1.4 and above.
Aidan, can you please get in contact with Martin Hollmichel to clarify how this information can be posted on OOo. Thanks.
Aidan: I talked with Martin Hollmichel and he said to make an announcement on dev@openoffice.org. I have posted this content to the list The filter project now contains 2 Java based modules xsltfilter and xsltvalidate. When building these modules, additional jar files are required in the classpath, unless j2sdk1.4 or greater is being used. The additional files that are required are : xalan.jar and xml-apis.jar (ver xalan-j_2_5_0) http://xml.apache.org/crimson/ crimson.jar (ver 1.1.3) http://xml.apache.org/xalan-j/index.html Also, when using these modules in OOo, these jars need to be present in the OOo classpath. To add these, click Tools->options->OpenOffice->Security and enter the file locations in the ClassPath entry box.
mh->svesik: can you please pick up Aidans post from dev@openoffice.org and update the build documentation on tools.openoffice.org.
build guides updated
Closing.