"mvn javadoc:test-javadoc" plugin build failures with Java8

[Craig Rodrigues]

Hi,

I recently tried to build a Jenkins plugin which I maintain with this JDK version:

openjdk version "1.8.0_77"
OpenJDK Runtime Environment (build 1.8.0_77-b03)
OpenJDK 64-Bit Server VM (build 25.77-b03, mixed mode)

and noticed some weird build failures when generating Javadoc.

These errors occur when I try to do mvn release:prepare release:perform .

I narrowed things down and found that I could reproduce the problem by doing

mvn javadoc:test-javadoc.

I know that Java8 is not (yet) the officially supported version to build

Jenkins plugins with, but I was wondering if people are encountering this.

What is the best way to fix this?

For example, I am including the errors I get when building
htpts://github.com/jenkinsci/jenkins with mvn javadoc:test-javadoc.

 

--

Craig

[Michael Neale]

I had this problem some months ago when releasing and the javadoc phase - I never did get to the bottom of it. 

Can you paste the error you saw with it? 

[Daniel Spilker]

See http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html

Daniel

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/91cce6a0-3dab-4266-a60a-939f30d92e25%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Craig Rodrigues]

Hi,

Thanks, that blog posting is informative.

It looks like Java 8 has become more aggressive about rejecting invalid constructs in Javadoc comments.

The blog's advice for using -Xdoclint:none in the POM file only works with Java 8 and
will break building with Java 7 or Java 6.

Something like this is required:
http://stackoverflow.com/questions/27728733/javadoc-error-invalid-flag-xdoclintnone-when-i-use-java-7-but-it-works-i

The other approach is to fix the code so that Javadoc cleanly compiles on Java 7 or 8.

--

Craig

On Tue, Apr 5, 2016 at 12:01 AM, Daniel Spilker <ma...@daniel-spilker.com> wrote:

See http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html

Daniel

[Jesse Glick]

On Mon, Apr 4, 2016 at 10:16 PM, Craig Rodrigues <rod...@freebsd.org> wrote:
> What is the best way to fix this?

In the time it took you to write this message, you could have fixed
the (legitimate!) errors which prevented your plugin from being
released using JDK 8. Just search for lines with `error:` and save the
`warning:` lines for a rainy day.