Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 13 May 2011 16:36:47 +0000 (UTC)
From: "Eric Yang (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <2100193567.10536.1305304607579.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2108193596.3999.1305137747997.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-2483) Clean up duplication of
 dependent jar files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eric Yang commented on MAPREDUCE-2483:
--------------------------------------

Nicholas, I have a patch for hdfs in HDFS-1917.  It would be really helpful, if you can review it.  Thanks

> Clean up duplication of dependent jar files
> -------------------------------------------
>
>                 Key: MAPREDUCE-2483
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2483
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.23.0
>            Reporter: Eric Yang
>
> For trunk, the build and deployment tree look like this:
> hadoop-common-0.2x.y
> hadoop-hdfs-0.2x.y
> hadoop-mapred-0.2x.y
> Technically, mapred's the third party dependent jar files should be fetch from hadoop-common and hadoop-hdfs.  However, it is currently fetching from hadoop-mapred/lib only.  It would be nice to eliminate the need to repeat duplicated jar files at build time.
> There are two options to manage this dependency list, continue to enhance ant build structure to fetch and filter jar file dependencies using ivy.  On the other hand, it would be a good opportunity to convert the build structure to maven, and use maven to manage the provided jar files.

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