You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@solr.apache.org by "Eric Pugh (Jira)" <ji...@apache.org> on 2022/10/18 21:38:00 UTC

[jira] [Resolved] (SOLR-16364) Evaluate using a shared Inspection Profile in IntelliJ

     [ https://issues.apache.org/jira/browse/SOLR-16364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Pugh resolved SOLR-16364.
------------------------------
    Resolution: Abandoned

Abandoning this idea because it appears we have a plethora of other tools to help us monitor code quality, and that this is also very intellj specific...   Plus, my underlying reason for wanting this, the thousands of warnings, well, they are being chipped away!

> Evaluate using a shared Inspection Profile in IntelliJ
> ------------------------------------------------------
>
>                 Key: SOLR-16364
>                 URL: https://issues.apache.org/jira/browse/SOLR-16364
>             Project: Solr
>          Issue Type: Sub-task
>          Components: Build
>    Affects Versions: main (10.0)
>            Reporter: Eric Pugh
>            Assignee: Eric Pugh
>            Priority: Minor
>         Attachments: Gradle Default for Java test code.png, Screenshot at Aug 31 12-22-03.png, Screenshot at Aug 31 13-03-25.png
>
>
> IntelliJ uses a "Inspection Profile" to decide what to flag as problems.   It would be nice if we as a community used a shared one that reflected what we think are problems and what are not...   Similiar thinking as our use of code style tooling or some of the decisions we've made around forbidden api's.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org