Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/347
@mmiklavc Good question. We definitely need to exclude the SLF4J bindings
that we don't use. The most common one is the Log4J2 binding that Storm brings
along ("org.apache.logging.log4j:log4j-slf4j-impl").
It could be argued that we don't need to exclude the binding we are using
("org.slf4j:slf4j-api") and control the version through dependency management
as you suggest. The downside I see there though is that if we ever did want to
change the logging implementation we would have to go through all the poms and
exclude that binding (what's already been done here). As it stands, changing
the logging implementation is as simple as changing the binding in the
metron-platform/analytics pom files and adding logging configuration files.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
