Mailing-List: contact hama-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hama-dev@incubator.apache.org
Date: Fri, 20 Jan 2012 11:28:40 +0000 (UTC)
From: "Thomas Jungblut (Created) (JIRA)" <jira@apache.org>
To: hama-dev@incubator.apache.org
Message-ID: 
 <1063053871.59662.1327058920180.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HAMA-491) Add Maven Release Target
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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
             Fix For: 0.4.0


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