Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6829#issuecomment-113429762
The idea for publishing the assembly (which BTW is not that big as it
should contain only the sink code + scala + common lang 3) is same as that
of current publishing of package JAR - so that people can directly download
the JAR and put it in the Flume to run the sink. So the only difference
compared to what is the current behavior is that instead of publishing just
sink code, we will publish sink code + scala + common lang 3, which makes
it more self contained.
On Fri, Jun 19, 2015 at 12:52 AM, Sean Owen <[email protected]>
wrote:
> Oh, I didn't realize you wanted to publish the assembly JAR. I don't think
> it makes sense to publish assemblies as Maven artifacts. Right? anyone
that
> uses it via Maven does not want an assembly and it causes a bunch of
> problems. So no please don't publish the assembly that way.
>
> You just need a target to build the assembly right? that's just a matter
> of adding a plugin.
>
> (You can publish multiple artifacts under different *classifiers* for one
> group/artifact but this isn't the situation that this would be used.)
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/6829#issuecomment-113417003>.
>
---
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]
