-
Notifications
You must be signed in to change notification settings - Fork 76
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
SLF4J loggers will not work because they were created during the default configuration phase of the underlying logging system. #175
Comments
@rokob can you take a look at this when you get a chance? |
Yeah I am looking right now, I'm not sure if this is a problem other than being noise |
I think this is saying that Rollbar uses SLF4J for its own logging and therefore an appender which calls into Rollbar creates a bit of recursion so the logging inside Rollbar won't work during the SLF4J setup phase. Afterwards things will work just fine. But I'm not sure why this doesn't happen in every project rather than just here in tests. |
Is this just a warning or does it actually prevent code from compiling and running? |
@Ghilteras, is this preventing code from compiling/running or is it just a warning? |
@brianr It looks like it's just a warning |
The rollbar logger early initialization WARN causes a lot of log messages to be printed by logback.
|
Hi, I'm getting this errors during my
mvn test
This happens with
rollbar-java 1.4.0
andlombok 1.18.6
Not sure what's needed to do here, any hints? The
substituteLogger
link above does not say anything interesting about it.The text was updated successfully, but these errors were encountered: