[
https://issues.apache.org/jira/browse/MAHOUT-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Drew Farris updated MAHOUT-224:
-------------------------------
Status: Open (was: Patch Available)
Good point about junit Isabel, thanks.
I'm wondering about Hadoop however, it doesn't need to be in the .job file
certainly, but doesn't it need to be present for the junit tests or any of the
utils that work with Sequence files?
FWIW, in light of the commit for MAHOUT-225, I need to rework this patch. I'll
be sure to set junit to test then, and do what ever results from any further
conversation about hadoop. I should be able to get to it within the next few
days.
> Dependency Cleanup
> ------------------
>
> Key: MAHOUT-224
> URL: https://issues.apache.org/jira/browse/MAHOUT-224
> Project: Mahout
> Issue Type: Improvement
> Affects Versions: 0.2
> Reporter: Drew Farris
> Assignee: Drew Farris
> Priority: Minor
> Attachments: mahout-224.patch
>
>
> In preparation for the binary release work described in MAHOUT-215, here's a
> minor patch that does some some cleanup on the poms.
> The hadoop and junit dependency versions are now established using the
> dependencyManagement section of the parent pom in mahout/maven/pom.xml
> A large number of transitive dependencies from the hadoop pom are now
> excluded there as well -- these were not necessary previously because the
> hadoop dependency was hand-rolled and did not include them. With the update
> to the hadoop 0.20.2-SNAPSHOT, they now become required.
> Also, the parent pom no longer has mahout/pom.xml as its parent, this allows
> binary packaging to be performed in mahout/pom.xml after the build of all of
> the other sub-modules is complete.
> Also, removed the javamail dependency -- was there a reason this was present?
> Verified that build and unit tests complete.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
