[
https://issues.apache.org/jira/browse/LUCENE-7129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206555#comment-15206555
]
Uwe Schindler commented on LUCENE-7129:
---------------------------------------
bq. Uwe, your "Quick'n'dirty" method would only work for entire classes that
have the @lucene.internal annotation - there are places where the annotation is
on individual methods.
I know, because of that I gave also the 2nd way ("clean approach"). This is
documented like that on Javadoc's documentation [FAQ
page|http://www.oracle.com/technetwork/java/javase/documentation/index-137483.html#exclude]
at Oracle. They refer to a "custom doclet" to do more filtering, but don't
give an example. The example above is a possible "cheap & elegant"
implementation - of course violating forbiddenapis (internal packages, we have
to exclude).
> Prevent @lucene.internal annotated classes from being in Javadocs
> -----------------------------------------------------------------
>
> Key: LUCENE-7129
> URL: https://issues.apache.org/jira/browse/LUCENE-7129
> Project: Lucene - Core
> Issue Type: Task
> Components: general/javadocs
> Reporter: David Smiley
> Priority: Minor
>
> It would be cool if we could prevent {{@lucene.internal}} classes from
> appearing in Javadocs we publish. This would further discourage use of
> internal Lucene/Solr classes that are public not for public consumption but
> only public so that the code can be accessed across Lucene/Solr's packages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
