Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2673#issuecomment-59468461
Hm - is there any workaround to that? We don't actually need to publish the
parent pom anyways if we are using effective poms. Could we just install the
other modules only and not the parent?
The current approach also adds Guava logic to the parent pom which doesn't
make much sense. I think ideally we'd just have a very simple "dummy"
relocation (e.g. without any exclusions) in the parent and the existing shading
stuff around guava would be in `core/pom.xml`. Does the NPE go away if you do
that?
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
