Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4998#issuecomment-78534488
@liorchaga I was thinking that Spark would just use log4j 2, and include
the log4j 1.2 bridge, so that no matter what, user apps would see the classes
they need. I don't know if it means users would have to migrate config -- would
log4j 2 + bridge not let them use their current config?
Otherwise, this is a pretty tough one. It's another symptom of classpath
leakage, although this one is harder to deal with than usual. I'm hesitant to
complicate things with another build profile, because I don't think Spark would
make releases with log4j 2 flavors just for this anyway. The thing is, your app
would work on your specially-built Spark but not others, and perhaps vice versa.
It's a sticky one for sure. If anyone has other approaches, maybe post them
on the JIRA discussion?
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
