[
https://issues.apache.org/jira/browse/MAHOUT-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042823#comment-13042823
]
Sean Owen commented on MAHOUT-699:
----------------------------------
Question: what do we even think about rolling mahout-utils into said
mahout-integration module?
There's no harm in keeping them separate if they truly serve different
purposes. I am not sure if they do now; both seem to have stuff that connects
stuff in core/ to other systems, formats, containers, etc. (And a few things in
there are arguably examples/.)
I am mildly in favor of this on grounds of simplification, but am open to
thoughts here?
> Rename taste-webapp module to integration; move integration code there from
> examples
> ------------------------------------------------------------------------------------
>
> Key: MAHOUT-699
> URL: https://issues.apache.org/jira/browse/MAHOUT-699
> Project: Mahout
> Issue Type: Improvement
> Components: Collaborative Filtering
> Affects Versions: 0.5
> Reporter: Sean Owen
> Assignee: Sean Owen
> Fix For: 0.6
>
>
> Per discussion on the mailing list we need a more rationalized approach to
> "integration" code of the sort that lives in bits in examples, in
> taste-webapp, and of the sort mentioned on the mailing list in the context of
> MongoDB.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
