Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/2673#issuecomment-60003900
Hey @ScrapCodes @pwendell,
Funny thing. I've been playing with a different part of the build and I've
found out I need exactly this to get what I wanted to work. I think I found a
workaround that doesn't require a new plugin, although it's not pretty.
What you can do is create a "dummy" sub-module that just publishes an empty
jar (or a jar with ay random file, it really doesn't matter). In the projects
where you want to publish the effective pom, add a call to the
maven-shade-plugin that only shades this dummy dependency, and actually
excludes all files from it in the `filters` section if needed.
That has both the effect of not packaging anything else in the final jar,
and also removing the dummy dependency from the published pom. But well, it's
pretty ugly.
---
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
