On Mon, Apr 4, 2016 at 10:16 PM, Craig Rodrigues 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
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
See http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html
Daniel
On Tue, Apr 5, 2016 at 7:25 AM, Michael Neale wrote:
> 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
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?
On Tuesday, April 5, 2016 at 12:16:28 PM UTC+10, Craig Rodrigues wrote:
>
> Hi,
>
> I recently tried to build a Jenkins plugin which I
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