You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Drew Farris (JIRA)" <ji...@apache.org> on 2009/12/09 15:00:18 UTC
[jira] Created: (MAHOUT-215) Provide jars with mahout release.
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
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.
[jira] Assigned: (MAHOUT-215) Provide jars with mahout release.
Posted by "Jake Mannix (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jake Mannix reassigned MAHOUT-215:
----------------------------------
Assignee: Jake Mannix
> 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
> Assignee: Jake Mannix
> 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: 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.
[jira] Commented: (MAHOUT-215) Provide jars with mahout release.
Posted by "Grant Ingersoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805931#action_12805931 ]
Grant Ingersoll commented on MAHOUT-215:
----------------------------------------
Just an FYI, we need to make sure we can legally include all the JARs for the dependencies, if that is what this patch does.
> 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
> Assignee: 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: 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.
[jira] Updated: (MAHOUT-215) Provide jars with mahout release.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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: https://issues.apache.org/jira/browse/MAHOUT-215
> 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: 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.
[jira] Commented: (MAHOUT-215) Provide jars with mahout release.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790560#action_12790560 ]
Drew Farris commented on MAHOUT-215:
------------------------------------
After some research, it seems the better approach would be to remove the parent-child relationship between mahout/maven/pom.xml and mahout/pom.xml. This will allow all of the binary artifact assembly to happen in mahout/pom.xml which would get executed after all of the child modules are built. The patch attached to MAHOUT-224, facilitates this change.
> 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
>
> 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.
[jira] Commented: (MAHOUT-215) Provide jars with mahout release.
Posted by "Jake Mannix (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828460#action_12828460 ]
Jake Mannix commented on MAHOUT-215:
------------------------------------
Ooops! committed r905524
> 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
> Assignee: Jake Mannix
> 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: 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.
[jira] Assigned: (MAHOUT-215) Provide jars with mahout release.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Drew Farris reassigned MAHOUT-215:
----------------------------------
Assignee: Drew Farris (was: Jake Mannix)
> 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
> Assignee: 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: 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.
[jira] Updated: (MAHOUT-215) Provide jars with mahout release.
Posted by "Sean Owen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen updated MAHOUT-215:
-----------------------------
Fix Version/s: 0.3
> 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.
[jira] Assigned: (MAHOUT-215) Provide jars with mahout release.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Drew Farris reassigned MAHOUT-215:
----------------------------------
Assignee: Jake Mannix (was: Drew Farris)
> 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
> Assignee: Jake Mannix
> 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: 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.
[jira] Commented: (MAHOUT-215) Provide jars with mahout release.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805910#action_12805910 ]
Drew Farris commented on MAHOUT-215:
------------------------------------
Thanks for the review and commit Jake
> 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
> Assignee: Jake Mannix
> 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: 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.
[jira] Commented: (MAHOUT-215) Provide jars with mahout release.
Posted by "Sean Owen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804270#action_12804270 ]
Sean Owen commented on MAHOUT-215:
----------------------------------
Is this resolved then -- the .jars are output to target, right? I see them at least.
> 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.
[jira] Closed: (MAHOUT-215) Provide jars with mahout release.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Drew Farris closed MAHOUT-215.
------------------------------
> 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
> Assignee: 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: 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.
[jira] Commented: (MAHOUT-215) Provide jars with mahout release.
Posted by "Jake Mannix (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805824#action_12805824 ]
Jake Mannix commented on MAHOUT-215:
------------------------------------
This patch still applies cleanly, and makes what you say it makes, lots of nice jars and jobs and javadocs and dependent libs.
Good stuff, looks commit-worthy!
> 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
>
> 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: 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.
[jira] Commented: (MAHOUT-215) Provide jars with mahout release.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805942#action_12805942 ]
Drew Farris commented on MAHOUT-215:
------------------------------------
bq. Just an FYI, we need to make sure we can legally include all the JARs for the dependencies, if that is what this patch does.
Ahh, that's a good point. Yes, this is what the patch does, we probably need to include license files for some of them. I will track them down and submit a followup patch.
> 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
> Assignee: 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: 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.
[jira] Updated: (MAHOUT-215) Provide jars with mahout release.
Posted by "Jake Mannix (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jake Mannix updated MAHOUT-215:
-------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed revision 903989.
> 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
> Assignee: Jake Mannix
> 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: 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.
[jira] Updated: (MAHOUT-215) Provide jars with mahout release.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Drew Farris updated MAHOUT-215:
-------------------------------
Status: Patch Available (was: Open)
> 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
>
> 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: 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.
[jira] Commented: (MAHOUT-215) Provide jars with mahout release.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (MAHOUT-215) Provide jars with mahout release.
Posted by "Drew Farris (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAHOUT-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828430#action_12828430 ]
Drew Farris commented on MAHOUT-215:
------------------------------------
It looks like there might have been a problem with this commit -- the files under src/main/assembly weren't created.
> 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
> Assignee: 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: 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.