[
https://issues.apache.org/jira/browse/SPARK-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587962#comment-16587962
]
Sean Owen commented on SPARK-6305:
----------------------------------
It was a mess. Excluding dependencies is an ongoing issue because other
dependencies change their dependencies. However, I think tools like the
enforcer plugin can help detect this.
I think the code has to use some specific logging framework to do its work, but
it can be shaded to keep it out of the user classpath. This could be a good
goal for Spark 3.0. However i am also not sure how much trouble the existing
log4j 1.x causes users?
Yes, it does entail updating users and tests' log configuration, which is why
it might be something for 3.0. But sure, if there's no real downside and some
upsides to doing it, I'm not against it.
> Add support for log4j 2.x to Spark
> ----------------------------------
>
> Key: SPARK-6305
> URL: https://issues.apache.org/jira/browse/SPARK-6305
> Project: Spark
> Issue Type: Improvement
> Components: Build
> Reporter: Tal Sliwowicz
> Priority: Minor
>
> log4j 2 requires replacing the slf4j binding and adding the log4j jars in the
> classpath. Since there are shaded jars, it must be done during the build.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
