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

LoggerFactory should check for SLF4J API instead of implementation. #202

Open
rob-valor opened this issue Jan 5, 2024 · 1 comment
Open

Comments

@rob-valor
Copy link

Describe the bug
LoggerFactory should check for SLF4J API (org.slf4j.Logger) instead of the implementation (org.slf4j.impl.StaticLoggerBinder), just like it is done for Log4J2

Additional context
The issue now is that a message is incorrectly printed to the console, altough SLF4J is on the classpath and the com.atomikos.logging.Slf4jLogger instance is not used, but is should be.

I understand that this project is not intended for support - because bug reports may or may not be considered for inclusion some day (in a future release). If this is issue is important to me then I can go to https://www.atomikos.com/Main/SupportOverview and arrange a paid support subscription.

@pascalleclercq
Copy link
Contributor

In that case, we may select sl4j logging framework without having any implementation in the classpath ? Do I miss something ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants