[
https://issues.apache.org/jira/browse/MAHOUT-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579673#comment-14579673
]
ASF GitHub Bot commented on MAHOUT-1706:
----------------------------------------
Github user andrewpalumbo commented on the pull request:
https://github.com/apache/mahout/pull/133#issuecomment-110522411
It should not (negatively) affect the shell classpath, since all of the
necessary dependencies are either packaged with {{mahout-spark-*.jars}} or in
the classpath returned by {{${SPARK_HOME}/bin/compute-classpath.sh}}.
This patch actually does not affect the classpath of a source build at all.
It only prevents the release process from packaging dependency jars into the
{{/lib}} dir of the binary distribution artifact.
However since it does add all of the jars in the {{/lib}} directory of the
binary build for any mahout command line flavor (spark, MR, h2o), I have been
hesitant to push it without more extensive testing (cluster and local).
I am going to close this for now and investigate a better approach.
> Remove dependency jars from /lib in mahout binary distribution
> --------------------------------------------------------------
>
> Key: MAHOUT-1706
> URL: https://issues.apache.org/jira/browse/MAHOUT-1706
> Project: Mahout
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Andrew Palumbo
> Assignee: Andrew Palumbo
> Fix For: 0.11.0
>
>
> The mahout distribution currently is shipping ~56 MB of dependecy jars in the
> /lib directory of the distribution. These are only added to the classpath by
> /bin/mahout in the binary distribution. It seems that we can remove them from
> the distribution. (we need to get the size of the distribution down)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
