[
https://issues.apache.org/jira/browse/MAHOUT-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Drew Farris updated MAHOUT-311:
-------------------------------
Attachment: MAHOUT-311.patch
In addition to the goals of this issue, this patch adjusts the way that
artifacts are pulled together for the binary release so that maven doesn't have
to do as much work wrt resolving dependencies.
Instead of using the moduleSet/binary stanzas to collect the submodules, they
are included as explicit filesets instead and all dependencies are pulled in
from the examples project (which is the tail of Mahout's dependency chain).
This makes the assembly descriptor more verbose but prevents the large number
of warnings related to dependencies already existing in the assembly.
> Update assemblies to include components of launcher script from MAHOUT-301
> --------------------------------------------------------------------------
>
> Key: MAHOUT-311
> URL: https://issues.apache.org/jira/browse/MAHOUT-311
> Project: Mahout
> Issue Type: Sub-task
> Affects Versions: 0.3
> Environment: linux, bash.
> Reporter: Drew Farris
> Fix For: 0.3
>
> Attachments: MAHOUT-311.patch
>
>
> Update the release assemblies to include an executable bin/mahout script and
> the contents of the conf directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
