[ 
https://issues.apache.org/jira/browse/LUCENE-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800283#action_12800283
 ] 

Michael McCandless commented on LUCENE-2209:
--------------------------------------------

We can start by making @internal expand to a consistent warning in the javadoc 
(maybe start from oal.util.cache.DBLRUCache's warning?)?  I'll pull together a 
proposed set of classes/methods that we should add @internal to.

I think @expert is a different concept than @experimental, though, it may not 
warrant its own tag because merely putting "Expert:" in front of the javadocs 
seems OK?

I would actually prefer bold, not red -- I think the red is overkill ;)  I like 
the current wording.

> add @experimental javadocs tag
> ------------------------------
>
>                 Key: LUCENE-2209
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2209
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: Javadocs
>            Reporter: Robert Muir
>         Attachments: LUCENE-2209.patch
>
>
> There are a lot of things marked experimental, api subject to change, etc. in 
> lucene.
> this patch simply adds a @experimental tag to common-build.xml so that we can 
> use it, for more consistency.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org

Reply via email to