[
https://issues.apache.org/jira/browse/SPARK-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Grover resolved SPARK-1184.
--------------------------------
Resolution: Fixed
> Update the distribution tar.gz to include spark-assembly jar
> ------------------------------------------------------------
>
> Key: SPARK-1184
> URL: https://issues.apache.org/jira/browse/SPARK-1184
> Project: Spark
> Issue Type: Bug
> Components: Build
> Affects Versions: 0.9.0
> Reporter: Mark Grover
> Assignee: Mark Grover
> Fix For: 0.9.0
>
>
> This JIRA tracks 2 things:
> 1. There seems to be something going on in our assembly generation logic
> because of which are two assembly jars.
> Something like:
> {code}spark-assembly_2.10-1.0.0-SNAPSHOT.jar{code}
> and
> {code}spark-assembly_2.10-1.0.0-SNAPSHOT-hadoop2.0.5-alpha.jar{code}
> The former is pretty bogus and doesn't contain any class files and should be
> gotten rid of. The latter contains all the good stuff. It essentially is the
> uber jar generated by the maven-shade-plugin
> 2. The current bigtop-dist profile that builds the maven assembly (a .tar.gz
> file) using the maven-assembly-plugin includes the bogus jar and not the
> legit spark-assembly jar. We should get rid of the first one from this
> assembly (which would happen when we fix #1) and put the legit uber jar in it.
> 3. Also, the bigtop-dist profile is meant to exclude the hadoop related jars
> from the distribution. It does a good job of doing so for org.apache.hadoop
> jars but misses the avro and zookeeper jars that are also provided by hadoop
> land.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
