Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 14 Feb 2011 23:11:57 +0000 (UTC)
From: "Eric Yang (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <221848315.16075.1297725117548.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (HADOOP-6255) Create an rpm integration project
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eric Yang commented on HADOOP-6255:
-----------------------------------

Allen> Why would maven make a difference?

The value in testing RPM installation would be to verify the RPM dependencies are correct.
The current ant setup has everything bundled in hadoop-core-*.jar file, and the single rpm contains both server and client.  It is not possible to componentized RPMs, and test RPM dependencies.  Therefore, the installation test is more meaningful after hadoop has been modularized.

I plan to revise the packages after maven project is done for ensuring deployment setup is inline with the document.

> Create an rpm integration project
> ---------------------------------
>
>                 Key: HADOOP-6255
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6255
>             Project: Hadoop Common
>          Issue Type: New Feature
>    Affects Versions: 0.20.100
>            Reporter: Owen O'Malley
>            Assignee: Eric Yang
>             Fix For: 0.20.100
>
>         Attachments: HADOOP-6255-branch-0.20-security.patch, HADOOP-6255.patch, deployment.pdf
>
>
> We should be able to create RPMs for Hadoop releases.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira