hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7560) Make hadoop-common a POM module with sub-modules (common & alfredo)
Date Mon, 22 Aug 2011 20:34:29 GMT

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

Alejandro Abdelnur commented on HADOOP-7560:
--------------------------------------------

@Arun, I assume you are referring to the moving common/hdfs to submodules. If so, we just
started the discussion here. I don't see any proposal/agreement yet.

The current set of Maven modules is a follows (the '*' means that are aggregator Maven modules,
type POM, no code in them):

{code}
trunk/
      hadopo-project/
      hadoop-project-dist/
      hadoop-assemblies/
      hadoop-annotations/
      hadoop-alfredo/
      hadoop-common/
      hadoop-hdfs/
      hadoop-mapreduce/*
                       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/
{code}

We could do something like (adding hoop modules to HDFS to have more comprehensive examples).
I'm using *AG* as a module label to indicate it is an aggregator and no-code/artifact is produced
from that module:

{code}
trunk/
      hadopo-project/
      hadoop-project-dist/
      hadoop-assemblies/
      hadoop-annotations/
      hadoop-common-AG/*
                    hadoop-alfredo/
                    hadoop-common/
      hadoop-hdfs-AG/*
                  hadoop-hdfs/
                  hadoop-hoop-client/
                  hadoop-hoop-server/
      hadoop-mapreduce-AG/*
                       hadoop-mr-client-AG/
                                        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-AG/
                                   hadoop-yarn-api/
                                   hadoop-yarn-common/
                                   hadoop-yarn-server/
{code}

I've introduce *AG* because, IMO, it would be confusing to have hadoop-common at two levels.
I've change all aggregator modules to *AG* for consistency.

Thoughts?


> 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
>
> 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

        

Mime
View raw message