Skip to content

Fix SLF4J config for logger in unit tests #54

Description

@tfmorris

The following warnings are currently being logged by the CI unit tests:

[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running com.google.refine.sampleExtension.SampleUtilTest
SLF4J(W): No SLF4J providers were found.
SLF4J(W): Defaulting to no-operation (NOP) logger implementation
SLF4J(W): See https://www.slf4j.org/codes.html#noProviders for further details.
SLF4J(W): Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier.
SLF4J(W): Ignoring binding found at [jar:file:/home/runner/.m2/repository/org/slf4j/slf4j-simple/1.7.36/slf4j-simple-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J(W): See https://www.slf4j.org/codes.html#ignoredBindings for an explanation.

Not sure if this is something inherited from the core or specific to this rep

Activity

  1. shubham09-patel commented on May 23, 2026

    @shubham09-patel

    Hi, I’d like to work on this issue.

    I’ll try to reproduce the warning locally by running the unit tests, then inspect the Maven dependencies to find where the old slf4j-simple:1.7.36 binding is coming from. If it is specific to this repository, I’ll update the test logging dependency/configuration and open a PR.

  2. tfmorris commented on May 26, 2026

    @tfmorris
    MemberAuthor

    Thanks for tackling this! Let us know if you need any help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions