Without investigating your specific setup in detail... Maven/Jenkins reports at lot of output when it fails with a JavaDoc 8 error. In order to locate the *actual* error, search in the build output for ": error:". This will take you to those lines that are relevant, e.g. in the console output of #332
[ERROR] /home/jenkins/jenkins-slave/workspace/UIMAJ-SDK_java8/uimaj-core/src/main/java/org/apache/uima/cas/impl/CASSerializer.java:674: error: @param name not found [ERROR] * @param bkwdCompatJira4743 set to true to write backward compatable delta, false to fix this bug [ERROR] ^ I'm pretty sure that build #333 would have completed ok if the build slave hadn't died. Cheers, -- Richard > On 08.08.2016, at 23:27, Marshall Schor <[email protected]> wrote: > > Hi, > > When I run a build on my Windows workstation, with Oracle Java 8_72, the > Javadoc > produces a bunch of [WARNINGS] about missing @param etc. > > > But these are warnings. > > When the Jenkins Java 8 build runs, these are [ERRORS]. > > I ran on my Windows workstation with mvn debug flag and can see that Java 8 > javadocs is being used, and I'm puzzled why it produces [WARNINGS] on my > machine, and [ERRORS] in Jenkins. > > > Also, I see that the Jenkins build with Java 8 used to work; it recently > stopped, due to the javadoc errors. The last good build with Java 8 was #327, > and looking at the console output, it was producing [WARNINGS], not [ERRORS] > > Anybody figure out what's going on? > > -Marshall
