[
https://issues.apache.org/jira/browse/LUCENE-9856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17306283#comment-17306283
]
Robert Muir commented on LUCENE-9856:
-------------------------------------
[~dweiss] i don't want to disable *entire ecj linter* for whole modules, that's
a bit too nuclear.
Instead I just want to "map-merge" configs on top of our base configuration,
rather than have a static file:
e.g. I'd like to set
{{org.eclipse.jdt.core.compiler.problem.unusedLocal=error}} across the board,
but set {{org.eclipse.jdt.core.compiler.problem.unusedLocal=ignore}} for the
queryparser and expression modules, until we have a chance to address the
generated code (maybe it requires antlr upgrade or something, etc)
I think it is likely a very simple use of java Properties class here to do this.
> Improve static analysis to catch dead code and other potential bugs
> -------------------------------------------------------------------
>
> Key: LUCENE-9856
> URL: https://issues.apache.org/jira/browse/LUCENE-9856
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
> Reporter: Zach Chen
> Priority: Minor
> Labels: build
> Attachments: LUCENE-9856.patch
>
>
> When working on PR [https://github.com/apache/lucene/pull/25,] we noticed
> that some dead code is not being caught during static analysis in gradle
> build, such as the *start* variable in the following code:
> [https://github.com/apache/lucene/blob/a5996dbecd4a6b4147d961260711a2cb6aeab3d3/lucene/facet/src/java/org/apache/lucene/facet/FacetsConfig.java#L446-L456]
>
> We may need to look at if additional javac compiler flag, or configuration
> for *error prone,* should be added to catch such bug as well as other
> potential ones.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
