Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7219#issuecomment-118951585
Marcelo - That is not a bad idea. It's not guaranteed it will work because
the underlying issue here is that having `test-jar` dependencies screws up the
maven shade plugin, and having a dedicated project would also require
`test-jar` dependencies. However, my guess is that the underlying cause here is
there is some corner case given the overall complexity of the dependency graph
and it's not taken into account in the maven shade plugin. So maybe this would
be simpler and it would just work.
For 1.4.1 I'd probably prefer to go with this approach since it's a bit
more conservative (introducing a new build module involves some potential
issues, such as making sure it is published correctly, etc). But I think for
the master branch we should introduce the new module and see if that works.
---
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]
