[
https://issues.apache.org/jira/browse/LUCENE-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17309810#comment-17309810
]
ASF subversion and git services commented on LUCENE-9881:
---------------------------------------------------------
Commit 690e256ec9f633dd06e34d87a437fa22c997019c in lucene's branch
refs/heads/main from Robert Muir
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=690e256 ]
LUCENE-9881: synchronize ECJ linter with Eclipse IDE (#46)
Co-authored-by: Uwe Schindler <[email protected]>
> synchronize ECJ linter with eclipse IDE
> ---------------------------------------
>
> Key: LUCENE-9881
> URL: https://issues.apache.org/jira/browse/LUCENE-9881
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Robert Muir
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently the IDE configuration is different from the linter.
> Some checks in the eclipse linter are currently disabled, but will show in
> the IDE and vice-versa.
> In the eclipse IDE, the experience is terrible: there are hundreds of useless
> warnings that won't actually fail lucene's build. It also enforces some
> things as error that make experimentation frustrating (such as unused imports)
> I think we should remove the duplication. linter config should have all of
> the compiler config. And we should just combine linter config, converting all
> errors into warnings, with the formatting settings into one file during
> {{gradle eclipse}}
> This way, if you see an eclipse warning, you know it will fail the lucene
> build. But you are no longer forced to fix unused imports to quickly try
> something out and run a unit test in the IDE, for example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
