Recnet changes in Javadoc/Javac also affect 3rd party code, is this going to be

Jonathan Gibbons jonathan.gibbons at oracle.com
Mon Mar 18 14:38:09 UTC 2019


Uwe,

You  can control the set of packages that are analyzed by doclint.

 From javac --help-extra

   -Xdoclint/package:[-]<packages>(,[-]<package>)*
         Enable or disable checks in specific packages. Each <package> 
is either the
         qualified name of a package or a package name prefix followed 
by .*, which
         expands to all sub-packages of the given package. Each 
<package> can be prefixed
         with - to disable checks for the specified package or packages.

-- Jon

On 3/18/19 3:36 AM, Uwe Schindler wrote:
> Hi,
>
> I installed OpenJDK 13 preview builds on Apache Lucene's Jenkins (to actually test some fixes with Hotspot), but the builds did not even pass compilation phase, so we can't even build Lucene:
> https://issues.apache.org/jira/browse/LUCENE-8729
>
> The question is now: We enable "doclint" checks in Lucene's code, but now it seems to also affect 3rd party code like Apache Lucene, if Javac has doclint enabled: Is this a bug and will this be part of JDK13, so will it also be complain in code outside JDK?
>
> My question: How to fix this and what is the correct spec that handles this for JDK 13?
>
> Uwe
>
> -----
> Uwe Schindler
> uschindler at apache.org
> ASF Member, Apache Lucene PMC / Committer
> Bremen, Germany
> http://lucene.apache.org/
>
>


More information about the javadoc-dev mailing list