[
https://issues.apache.org/jira/browse/METRON-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644629#comment-15644629
]
ASF GitHub Bot commented on METRON-541:
---------------------------------------
Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/347
@merrimanr Love this effort. We just went through something similar in
getting the apache curator versions lined up for the Storm upgrade support
ticket. Thinking more about it, I'm not sure we need to explicitly exclude all
of these dependencies. Can we try just an explicit declaration at the global
level? Per "Dependency mediation" from the Maven docs:
> You can always guarantee a version by declaring it explicitly in your
project's POM. Note that if two dependency versions are at the same depth in
the dependency tree, until Maven 2.0.8 it was not defined which one would win,
**but since Maven 2.0.9 it's the order in the declaration that counts: the
first declaration wins**.
I *think* our own explicit declarations should supersede the transitive
dependencies, which should clean up our poms quite a bit if I'm right about
that.
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Transitive_Dependencies
> Set log levels for Metron components
> ------------------------------------
>
> Key: METRON-541
> URL: https://issues.apache.org/jira/browse/METRON-541
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
> Priority: Critical
>
> When running unit or integration tests the log output is very verbose. This
> makes it difficult to determine what the problem is when something goes wrong
> and also intermittently causes Travis to hit it's output threshold and fail.
> The log levels should be consistent across all components and there should be
> logging profiles available for different scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
