hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2483) Clean up duplication of dependent jar files
Date Wed, 11 May 2011 18:28:49 GMT

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

Tsz Wo (Nicholas), SZE commented on MAPREDUCE-2483:

There are also duplicated dependent jars from codes and tests (e.g the same jar will appear
in both {{build/ivy/lib/hadoop-hdfs/common/}} and {{build/ivy/lib/hadoop-hdfs/test/}}).  See
if you want to fix it here.

> 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

View raw message