You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Edward J. Yoon (Commented) (JIRA)" <ji...@apache.org> on 2012/01/30 12:31:12 UTC

[jira] [Commented] (HAMA-491) Add Maven Release Target

    [ https://issues.apache.org/jira/browse/HAMA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196059#comment-13196059 ] 

Edward J. Yoon commented on HAMA-491:
-------------------------------------

Regarding yarn module, I'd like to release separately because of dependency problems.

Maybe like this?

 * hama-0.4-incubating.tar.gz
 * hama-0.4-yarn-incubating.tar.gz


                
> Add Maven Release Target
> ------------------------
>
>                 Key: HAMA-491
>                 URL: https://issues.apache.org/jira/browse/HAMA-491
>             Project: Hama
>          Issue Type: New Feature
>          Components: build 
>    Affects Versions: 0.3.0
>            Reporter: Thomas Jungblut
>            Priority: Blocker
>              Labels: newbie
>             Fix For: 0.4.0
>
>         Attachments: patch.txt
>
>
> We need to add a release target to maven:
> * "binary" release without sources, packed into a tar.gz archive
> * sources release without precompiled jars, as well packed into a tar.gz archive
> Pluspoints: Automagically pgp armoring of the created archive.
> You can pretty much just copy and paste the 0.3.0 release and just update the jars (core, example, add YARN and graph). Maybe there must be a depedency update done in the lib folder.
> One feature that must be included in 0.4.0 is HAMA-470, you have to make sure that the file is in the correct place.
> How to test:
> A user just has to set the hdfs address in the site config and is able to start the cluster without problems (run some examples etc).
> All packaging stuff can be done with the maven assembly plugin: http://maven.apache.org/plugins/maven-assembly-plugin/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira