Uwe,
In addition to my previous answer, I would also note that doclint only
applies to
source code being compiled; if code depends on other libraries, and those
libraries are made available in compiled form, then doclint will of
course not
be invoked for those libraries.
-- Jon
On 3/18/19 7:38 AM, Jonathan Gibbons wrote:
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
[email protected]
ASF Member, Apache Lucene PMC / Committer
Bremen, Germany
http://lucene.apache.org/
