Hi,
It appears Jenkins has been upgraded to Java 8 despite still having a
Java 7 directory. This is clear from the output from the Job that
failed for the 2.x branch:
[tika-2.x] $
/home/jenkins/jenkins-slave/tools/hudson.model.JDK/JDK_1.7_latest_/bin/java
-Xmx2g -Xms256m -XX:MaxPermSize=512m -cp
/home/jenkins/jenkins-slave/maven32-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.4/boot/plexus-classworlds-2.5.1.jar:/home/jenkins/tools/maven/apache-maven-3.0.4/conf/logging
jenkins.maven3.agent.Maven32Main
/home/jenkins/tools/maven/apache-maven-3.0.4
/home/jenkins/jenkins-slave/slave.jar
/home/jenkins/jenkins-slave/maven32-interceptor.jar
/home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 40932
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
MaxPermSize=512m; support was removed in *8.0*
This is fine except it's caused some of the warnings in the JavaDoc step
to turn to errors. To correct it we'd need to revert back to Java 7 or
we need to add the following plugin to the tika-parent/pom.xml (see
http://stackoverflow.com/questions/15886209/maven-is-not-working-in-java-8-when-javadoc-tags-are-incomplete)
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<additionalparam>-Xdoclint:none</additionalparam>
</configuration>
</plugin>
Do we want to downgrade Jenkins or should we just add the entry above to
the POM?
- Bob
