Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 23 Aug 2011 19:06:29 +0000 (UTC)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <906578293.6201.1314126389397.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1916833997.54971.1313795127492.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-7560) Make hadoop-common a POM module
 with sub-modules (common & alfredo)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arun C Murthy commented on HADOOP-7560:
---------------------------------------

I'm not sure another huge set of 'svn mv's to incorporate alfredo is in order.

If hadoop-common depends on hadoop-alfredo, why don't we just move alfredo into common and be done with?

The common jar isn't that big really, so anyone who depends on hadoop-alfredo could just depend on hadoop-common?

> Make hadoop-common a POM module with sub-modules (common & alfredo)
> -------------------------------------------------------------------
>
>                 Key: HADOOP-7560
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7560
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>             Fix For: 0.23.0
>
>
> Currently hadoop-common is a JAR module, thus it cannot aggregate sub-modules.
> Changing it to POM module it makes it an aggregator module, all the code under hadoop-common must be moved to a sub-module.
> I.e.:
> mkdir hadoop-common-project
> mv hadoop-common hadoop-common-project
> mv hadoop-alfredo hadoop-common-project
> hadoop-common-project/pom.xml is a POM module that aggregates common & alfredo

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