We can even think about reducing the numbers of different priority levels. Eclipse and IntelliJ use by default only 3 types: failure, warning, info. (if you consider priority==severity)
+1 to reducing to 3. Specially since everything by default is medium. It's already rare for an org to manually override the value in their ruleset, they probably don't need so much granularity.
Additionally, it could be interesting to add an orthogonal value: confidence (high / low). Ie: when UnnecessaryImport falls back to "best-effort" due to an incomplete auxclasspath, it could report violations at a lower confidence level.
Originally posted by @jsotuyod in #4059 (comment)
We can even think about reducing the numbers of different priority levels. Eclipse and IntelliJ use by default only 3 types: failure, warning, info. (if you consider priority==severity)
+1 to reducing to 3. Specially since everything by default is medium. It's already rare for an org to manually override the value in their ruleset, they probably don't need so much granularity.
Additionally, it could be interesting to add an orthogonal value: confidence (high / low). Ie: when
UnnecessaryImportfalls back to "best-effort" due to an incomplete auxclasspath, it could report violations at a lower confidence level.Originally posted by @jsotuyod in #4059 (comment)