Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable SLF4J warning "No SLF4J providers were found" #594

Open
st-cyrill opened this issue Jan 26, 2023 · 0 comments
Open

Disable SLF4J warning "No SLF4J providers were found" #594

st-cyrill opened this issue Jan 26, 2023 · 0 comments

Comments

@st-cyrill
Copy link

st-cyrill commented Jan 26, 2023

What feature do you want to see added?

Everyone knows, console says No SLF4J providers were found

SLF4J: No SLF4J providers were found.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#noProviders for further details.

I want to disable this warning message.
According to https://www.slf4j.org/codes.html#noProviders,
message is reported when no SLF4J providers could be found on the class path.

Can I do it in the following ways?

  1. Placing one (and only one) of slf4j-nop.jar slf4j-simple.jar, slf4j-reload4j.jar, slf4j-jdk14.jar or logback-classic.jar on the class path.
    If possible, could you contain a slf4j.jar (slf4j-nop.jar) file when building Docker image?

  2. Other way, can I change additional class-path in jenkins-agent and jenkins-agent.ps1?
    Currently, -cp agent.jar is hard coded. It is useful to add slf4j-nop.jar in class-path.

Thank you for reading.

Upstream changes

No response

@lemeurherve lemeurherve transferred this issue from jenkinsci/docker-inbound-agent Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants