Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

exclusion of slf4j-jboss-logmanager

See original GitHub issue

Describe the bug In our quarkus applications we use a custom extension to be able to log JSON with a particular format (not supported by any quarkus extension I’m aware of).

Since slf4j-jboss-logmanager is extending MarkerIgnoringBase and we would like to use SLF4J as facade with Markers, right now we are excluding slf4j-jboss-logmanager manually from a lot of dependencies.

Expected behavior Ideally slf4j-jboss-logmanager should not use MarkerIgnoringBase, so it could be used also in our case (don’t know if that is possible) but actually I would like to not forcing any SLF4J binding in quarkus.

Actual behavior A lot of effort to track down every single usage of slf4j-jboss-logmanager (I see it is a direct dependency for quarkus-core and quarkus-scheduler, at least).

To Reproduce N/A

Configuration N/A

Screenshots N/A

Environment (please complete the following information):

Output of uname -a or ver: Microsoft Windows [Version 10.0.17763.1757]
Output of java -version: openjdk 11
GraalVM version (if different from Java): N/A
Quarkus version or git rev: 1.11.3
Build tool (ie. output of mvnw --version or gradlew --version): Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)

Additional context I could provide a pull request or in general help with testing

Issue Analytics

State:
Created 3 years ago
Comments:29 (20 by maintainers)

Top GitHub Comments

1reaction

jamezpcommented, Jul 19, 2022

Released 1.2.0.Final https://github.com/jboss-logging/slf4j-jboss-logmanager/releases/tag/1.2.0.Final. It will take a bit for it to replicate over to Maven Central, but is in JBoss Nexus.

0reactions

dfa1commented, Aug 3, 2022

@clotton in our infrastructure we have something similar built in openshift but we (devs) can’t really control what is being added. So, I fear that there is nothing you can do in your quarkus application. Unless, of course, I’m missing something 😃

Top Results From Across the Web

How to exclude slf4j module in a war artifact? - JBoss.org

If you want to use your own version of slf4j jar then you can exclude the JBoss provided slf4j using "WEB-INF/jboss-deployment-structure.xml" ...

Exclude Jboss Slf4j implementation from Logging

I realized there was a dependency inserted inside the web appication manifest pointing to the org.slf4j jboss module.

JBoss module exclusion for slf4j not working when depending ...

The custom log4j/SLF4J context doesn't work when depending on another deployment via jboss-deployment-structure.xml . Environment. JBoss ...

jboss-logging : 3.2.1.Final - Maven Central Repository Search

... </Export-Package> <Import-Package> org.apache.log4j|org.apache.logging.log4j|org.slf4j|org.slf4j.spi|org.jboss.logmanager;resolution:=optional,* ...

SLF4J Error Codes

This warning, i.e. not an error, message is reported when no SLF4J providers could be found on the class path. Placing one (and...