You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was developing something to build elasticsearch indexes that uses SLF4J and found that it gave error messages because SLF4J was set up.
It is possible to set things up so that there is no commons logging dependency but that a stub is put in that routes commons logging through SLF4J, this is documented for use with Spring.
The main PITA involved is that users of the system will need to systematically suppress commons-logging from coming in a dependency otherwise strange things that can suck huge amounts of time can happen.
The text was updated successfully, but these errors were encountered:
Well, it happened.
I was developing something to build elasticsearch indexes that uses SLF4J and found that it gave error messages because SLF4J was set up.
It is possible to set things up so that there is no commons logging dependency but that a stub is put in that routes commons logging through SLF4J, this is documented for use with Spring.
The main PITA involved is that users of the system will need to systematically suppress commons-logging from coming in a dependency otherwise strange things that can suck huge amounts of time can happen.
The text was updated successfully, but these errors were encountered: