davsclaus opened a new pull request, #28118: URL: https://github.com/apache/camel/pull/28118
The camel-jbang-mcp server gets two SLF4J providers: Quarkus brings `slf4j-jboss-logmanager`, and camel-jbang-core brings `log4j-slf4j2-impl`. So SLF4J printed this on stderr each time the server started: ``` SLF4J(W): Class path contains multiple SLF4J providers. SLF4J(W): Found provider [org.slf4j.impl.JBossSlf4jServiceProvider@4808bc9b] SLF4J(W): Found provider [org.apache.logging.slf4j.SLF4JServiceProvider@70e38ce1] SLF4J(W): See https://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J(I): Actual provider is of type [org.slf4j.impl.JBossSlf4jServiceProvider@4808bc9b] ``` SLF4J used the provider of Quarkus. Which one it uses depends on the order of the classpath. ## What - camel-jbang-mcp excludes `log4j-slf4j2-impl` from its camel-jbang-core dependency. Quarkus logging is the only SLF4J provider, so the server logs as before, and SLF4J does not warn. - log4j-core stays, as camel-jbang-core uses it to configure the logging of a Camel it runs. ## Tests - All tests of camel-jbang-mcp pass (503). Their output no longer has the SLF4J warning. - The runner built from this branch starts without the warning, and stdout stays empty. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
