[
https://issues.apache.org/jira/browse/LUCENE-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410041#comment-13410041
]
Robert Muir commented on LUCENE-4202:
-------------------------------------
Can't we separate these issues though?
I think its ok to add the Fields check here, and populate the deprecated fields
(and maybe consider a separate ant instantiation that checks non-test fileset
for System.out & co).
Separately we could open an issue to deal with this virtual problem? It just
means our checker isn't as thorough as it is, but none of our checkers/tests
are perfect.
This all assumes Uwe doesn't wake up with a great solution :)
> allow check-forbidden-apis to look for fields too
> -------------------------------------------------
>
> Key: LUCENE-4202
> URL: https://issues.apache.org/jira/browse/LUCENE-4202
> Project: Lucene - Java
> Issue Type: New Feature
> Components: general/build
> Reporter: Robert Muir
> Assignee: Uwe Schindler
> Attachments: LUCENE-4202.patch
>
>
> Currently this supports classes and methods, but there are some deprecated
> fields in the java API, it would be nice to check for those, too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
