Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/8373#issuecomment-133798583
E.g., in 1.5.0-rc1, for the kafka-assembly project, maven will generate a
jar without any codes except some meta files in the target folder, see
https://repository.apache.org/content/repositories/orgapachespark-1137/org/apache/spark/spark-streaming-kafka-assembly_2.10/1.5.0-rc1/
for example.
Because outputPath was set, maven-shaded-plugin didn't replace
`spark-streaming-kafka-assembly_2.10-1.5.0-rc1.jar` with the new real assembly
jar. So maven just published this empty jar. By default, maven publishes the
file in target, rather than the path specified by `outputPath` of
maven-shaded-plugin.
That's why I removed `outputPath`. Then maven-shaded-plugin will replace
`spark-streaming-kafka-assembly_2.10-1.5.0-rc1.jar` with the new real assembly
jar in the same path (the default behavior of `maven-shaded-plugin`). So that
maven will publish the correct assembly jar.
---
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]
