[
https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804344#action_12804344
]
Drew Farris commented on MAHOUT-215:
------------------------------------
I need to do a bit more work on this one, the release tarballs built via mvn
install -Prelease don't currently include the jars. There should be a
mahout-VERSION-bin.tar.gz that contains jar files for each of the mahout
modules and all of the dependencies.
I'd like to take care of source and javadoc jars as a part of this too.
It may be worth holding off on this until the collections module structure is
sorted out, but I there are some things I can do before that's done.
> Provide jars with mahout release.
> ---------------------------------
>
> Key: MAHOUT-215
> URL: https://issues.apache.org/jira/browse/MAHOUT-215
> Project: Mahout
> Issue Type: Improvement
> Affects Versions: 0.2
> Reporter: Drew Farris
> Fix For: 0.3
>
>
> The 0.2 release of mahout does not include pre-built jars for the various
> mahout modules. An end user must be able to build the jars using maven or
> figure out how to retrieve them from the maven repository, which can be easy
> or difficult depending on the build tool being used. It would be convenient
> to provide binary jars in future mahout releases.
> One approach for doing this is described "Maven: the Definitive Guide",
> available on the web here:
> http://www.sonatype.com/books/maven-book/reference/assemblies-set-dist-assemblies.html
> The problem with the current project structure is described succinctly in the
> second paragraph of this page. The dependencies are structured in such a way
> so that the top-level mahout project is always built before core, utils,
> examples, etc, so that it is not a simple matter of adding or modifying the
> assembly of this project to include the child artifacts.
> Following the approach described in the resource above, a new module would be
> created below the top-level mahout project whose sole purpose is to bundle
> the distributions. This module would depend on all other projects that would
> be included in the distribution and thus be build only after all of the other
> modules are built. This assembly would wrap together both the sources and
> binary artifacts for each of the modules included in the release.
> Additionally, the release profile can be removed from the top level pom and
> the artifacts produced by the project assembly descriptor would no longer be
> needed.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
