You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Robert Muir (Jira)" <ji...@apache.org> on 2021/03/26 13:54:00 UTC

[jira] [Created] (LUCENE-9881) synchronize ECJ linter with eclipse IDE

Robert Muir created LUCENE-9881:
-----------------------------------

             Summary: 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


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: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org