[
https://issues.apache.org/jira/browse/HADOOP-16716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16976072#comment-16976072
]
Steve Loughran commented on HADOOP-16716:
-----------------------------------------
There is a risk of this change will have traumatic consequences for every
single application which uses the code and expects there to be logger on it.
That includes all the other modules and their tests but downstream things too.
Certainly, it will break my downstream applications which have had enough
problems with guava updates already.
If people don't want Log4J on the CP, they are free to exclude the relevant
dependencies. And I hope the shaded client doesn't export these.
Therefore I am in favour of leaving things as they are.
please tag with versions, components etc.
> slf4j-log4j12 Should Not Be Included as Dependency
> --------------------------------------------------
>
> Key: HADOOP-16716
> URL: https://issues.apache.org/jira/browse/HADOOP-16716
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: David Mollitor
> Assignee: David Mollitor
> Priority: Major
>
> The project should be using 'slf4j-api' to log to the SLF4J framwork, but the
> end-project, the project that includes hadoop-commons should be specifying
> the specific binding to use.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
