Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Wed, 24 Aug 2011 20:24:30 +0000 (UTC)
From: "Eric Yang (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <349666913.10626.1314217470611.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=13090454#comment-13090454 ] 

Eric Yang commented on HADOOP-7560:
-----------------------------------

Alejandro, the proposed approaches are two extreme models.  How about we have a sensible approach to group top level modules and submodules?

For example:

{noformat}
trunk/
      hadopo-project/ (f)
      hadoop-common/ (f)
      hadoop-hdfs/ (h)
                       hadoop-hdfs-http-client/ (f) (this is hoop)
                       hadoop-hdfs-http-server/ (f) (this is hoop)
      hadoop-mapreduce/ (h) (*)
                       hadoop-mr-client/ (*)
                                        hadoop-mapreduce-client-app/
                                        hadoop-mapreduce-client-common/
                                        hadoop-mapreduce-client-core/
                                        hadoop-mapreduce-client-hs/
                                        hadoop-mapreduce-client-jobclient/
                                        hadoop-mapreduce-client-shuffle/                                       
                       hadoop-yarn/ (*)
                                   hadoop-yarn-api/
                                   hadoop-yarn-common/
                                   hadoop-yarn-server/
{noformat}

In the proposed format, the structure of the tree is driven by the context and importance of the module.

IMHO, hadoop-project-dist, hadoop-assemblies, hadoop-annotations should not be modules.  They are small plugins and can be grouped  as hadoop-project.  hadoop-auth should be part of hadoop-common.  This will remove the noise for the project organization.

> 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
>
>         Attachments: HADOOP-7560v1.patch, HADOOP-7560v1.sh
>
>
> 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