Github user srowen commented on the pull request: https://github.com/apache/incubator-spark/pull/573#issuecomment-34666426 Sorry, my meaning was: how about solving this by removing the guard? The guard is the problem. It's there to prevent executing the log4j config when log4j is not being used, but, I don't think anything bad happens if this executes when using some other logging. One would have shimmed in `log4j-over-slf4j` and it contains a no-op `PropertyConfiguration`, so this happily does nothing.
- [GitHub] incubator-spark pull request: Default log4j initial... pwendell
- [GitHub] incubator-spark pull request: Default log4j in... AmplabJenkins
- [GitHub] incubator-spark pull request: Default log4j in... AmplabJenkins
- [GitHub] incubator-spark pull request: Default log4j in... AmplabJenkins
- [GitHub] incubator-spark pull request: Default log4j in... AmplabJenkins
- [GitHub] incubator-spark pull request: Default log4j in... srowen
- [GitHub] incubator-spark pull request: Default log4j in... pwendell
- [GitHub] incubator-spark pull request: Default log4j in... srowen
- [GitHub] incubator-spark pull request: Default log4j in... pwendell
- [GitHub] incubator-spark pull request: Default log4j in... srowen
- [GitHub] incubator-spark pull request: Default log4j in... prb
- [GitHub] incubator-spark pull request: Default log4j in... aarondav
- [GitHub] incubator-spark pull request: Default log4j in... srowen
- [GitHub] incubator-spark pull request: Default log4j in... pwendell