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
Why does the JAR come packaged with an implementation instead of relying on the API? When deployed with other projects, it causes the multiple slf4j bindings issue.
The text was updated successfully, but these errors were encountered:
Dependency-check has an instance of slf4j in its lib directory as slf4j is not used by Ant. I'm double checking with @colezlaw - but if memory serves implementing a StaticLoggerBinder allows a library that uses SLF4j (in this case dependency-check) to route log messages to Ant.
Newer versions of slf4j appear to support the Java extensions mechanism to load services. We need to investigate changing our binding to use this instead of the static binder.
Why does the JAR come packaged with an implementation instead of relying on the API? When deployed with other projects, it causes the multiple slf4j bindings issue.
The text was updated successfully, but these errors were encountered: