[
https://issues.apache.org/jira/browse/MAHOUT-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012102#comment-13012102
]
Ted Dunning commented on MAHOUT-368:
------------------------------------
{quote}
Why not having a bundle artifact where all the Mahout submodules would be put
it a single jar?
{quote}
Julien,
I must be missing something here.
How is this not trivial for you to handle with maven?
If you are writing your own maven project (recommended), then
jar-with-dependencies will do what you want.
If you are extending Mahout (ok for prototypes), just put your code in the
examples job jar and all will be good.
Can you say more about what you are doing and how it doesn't work? (note that
this bug is closed as not a problem)
> should package core ,math and collections to one Jar package for hadoop
> recommendations
> ---------------------------------------------------------------------------------------
>
> Key: MAHOUT-368
> URL: https://issues.apache.org/jira/browse/MAHOUT-368
> Project: Mahout
> Issue Type: Improvement
> Components: Collaborative Filtering
> Affects Versions: 0.4
> Reporter: Han Hui Wen
> Assignee: Sean Owen
> Labels: classloader, hadoop, mahout
> Fix For: 0.4
>
>
> should package core ,math and collections to one Jar package for
> org.apache.mahout.cf.taste.hadoop.item.RecommenderJob.
> because RecommenderJob used classes (for example
> org.apache.mahout.math.VectorWritable )of the math module of mahout project,
> but math and core module is the separated jar package.
> so when work on the hadoop env ,the class of math module can not load to
> classloader in the datanode.
> it will cause class not found exception.
> the work around is package all mahout classes to one package manually.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
