[ODLPARENT-184] SpotBugs reports missing SLF4J implementation Created: 02/Jan/19  Updated: 19/Mar/19  Resolved: 19/Mar/19

Status: Resolved
Project: odlparent
Component/s: General
Affects Version/s: None
Fix Version/s: 4.0.9

Type: Bug Priority: Medium
Reporter: Robert Varga Assignee: Stephen Kitt
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Running spotbugs with maven-3.6.0 and odlparent-4.0.5+ reports the following:

[INFO] >>> spotbugs-maven-plugin:3.1.8:check (default-cli) > :spotbugs @ web-api >>>
[INFO]
[INFO] --- spotbugs-maven-plugin:3.1.8:spotbugs (spotbugs) @ web-api ---
[INFO] Fork Value is true
     [java] SLF4J: No SLF4J providers were found.
     [java] SLF4J: Defaulting to no-operation (NOP) logger implementation
     [java] SLF4J: See http://www.slf4j.org/codes.html#noProviders for further details.
[INFO] Done SpotBugs Analysis....
[INFO]
[INFO] <<< spotbugs-maven-plugin:3.1.8:check (default-cli) < :spotbugs @ web-api <<<
[INFO]
[INFO]
[INFO] --- spotbugs-maven-plugin:3.1.8:check (default-cli) @ web-api ---
[INFO] BugInstance size is 0
[INFO] Error size is 0
[INFO] No errors/warnings found
[INFO]

This seems to be harmless, but floods the logs. We should address the underlying problem, probably by adding a dependency to spotbugs.



 Comments   
Comment by Stephen Kitt [ 09/Jan/19 ]

4.0.8 ends up showing this because the SLF4J 1.8 dependency is carried by SpotBugs itself (from 3.1.9 onwards).

Generated at Wed Feb 07 20:27:51 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.