Kim Haase <[email protected]> writes: > Oh no! What did I do to mess up the docs build? I'm mystified by this > message. This is for a patch I committed a couple days ago -- the docs > build doesn't happen very often.
It looks like it was caused by a problem with the Java installation in the build environment rather than your patch. https://builds.apache.org/job/Derby-docs/ws/antoutput.log BUILD FAILED /home/jenkins/jenkins-slave/workspace/Derby-docs/trunk/build.xml:171: The following error occurred while executing this line: /home/jenkins/jenkins-slave/workspace/Derby-docs/trunk/build.xml:222: The following error occurred while executing this line: /home/jenkins/jenkins-slave/workspace/Derby-docs/trunk/DITA-OT1.1.2.1/conductor.xml:209: The following error occurred while executing this line: /home/jenkins/jenkins-slave/workspace/Derby-docs/trunk/DITA-OT1.1.2.1/ditatargets.xml:78: java.lang.UnsatisfiedLinkError: /home/jenkins/tools/java/IBMJava2-142/jre/bin/libawt.so: libXmu.so.6: cannot open shared object file: No such file or directory at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:2144) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:2004) at java.lang.Runtime.loadLibrary0(Runtime.java:824) at java.lang.System.loadLibrary(System.java:910) ... -- Knut Anders
