mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Drew Farris (JIRA)" <>
Subject [jira] Updated: (MAHOUT-215) Provide jars with mahout release.
Date Wed, 27 Jan 2010 22:12:34 GMT


Drew Farris updated MAHOUT-215:

    Attachment: MAHOUT-215.patch

This patch adds build directives that produce a number of artifacts when the release profile
is activated, e.g: with mvn clean install -Prelease

The artifacts generated include:

A binary release named mahout-{version}.{archiveformat} is produced in mahout/target. This
artifact contains:
* the mahout jar files (mahout-math, mahout-core, mahout-utils, mahout-examples)
* the mahout-taste-webapp.war
* job files from core and examples (do we really need both?)
* javadoc for math, core, utils, examples in docs
* all dependencies in lib
* KEYS, LICENSE.txt, NOTICE.txt and README.txt

A source release named mahout-{version}-src.{archiveformat} is produced in mahout/target.
 This artifact contains:
* sources for all modules including pom files, and extra files required for the build. I have
tested a full build and test complete successfully (mvn clean install)
* KEYS, LICENSE.txt, NOTICE.txt and README.txt

Archives are generated in gzip, bzip2 and zip format.

Source and javadoc jars are built for all modules as well. Maven should attach the assemblies
and source, javadoc jars as artifacts and they deployed alongside the build artifacts, but
I have not tested this.

Also did some dependency cleanup for the easymock deps and upped these to 2.5.2

> Provide jars with mahout release.
> ---------------------------------
>                 Key: MAHOUT-215
>                 URL:
>             Project: Mahout
>          Issue Type: Improvement
>    Affects Versions: 0.2
>            Reporter: Drew Farris
>             Fix For: 0.3
>         Attachments: MAHOUT-215.patch
> 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:
> 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.

View raw message