iemejia commented on pull request #13073: URL: https://github.com/apache/beam/pull/13073#issuecomment-723101054
Argh! I was afraid of that too, It clearly looks like a different classpath issue, that will explain why it breaks so weirdly. I think the simplest solution would be to let that module to provide its own log4j. The part that still does not make any sense to me is how the hcatalog module in Beam ends up resolving the new version of log4j? Can you spot which dependency is overwriting the version ? From a look at the module build.gradle file I don't see any of the Beam dependencies of hcatalog requiring log4j. I have checked in the [gradle scan](https://scans.gradle.com/s/6fi4yafhc37zc/dependencies?focusedDependencyView=versions&toggled=W1s4MF0sWzgwLDIxXSxbODAsMjEsWzExNDEwXV0sWzgwLDIxLFsxMTQxMCwxMTQxNF1dLFs4MCwyMSxbMTE0MTAsMTE0MTQsMTE0MTZdXV0) too and I just cannot see who is doing it ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
