[
https://issues.apache.org/jira/browse/HDFS-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032515#comment-13032515
]
Eric Yang commented on HDFS-1917:
---------------------------------
Patch for this jira is going to assume that hadoop-common third party jar files
can be referenced from HADOOP_HOME/lib until HADOOP-6255 and proposed
HADOOP_PREFIX take place. Where HADOOP_HOME is the PREFIX directory of
hadoop-common-0.2x.y = hadoop-hdfs-0.2x.y = hadoop-mapred-0.2x.y.
> Clean up duplication of dependent jar files
> -------------------------------------------
>
> Key: HDFS-1917
> URL: https://issues.apache.org/jira/browse/HDFS-1917
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: build
> Affects Versions: 0.23.0
> Environment: Java 6, RHEL 5.5
> 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, hdfs's the third party dependent jar files should be fetch from
> hadoop-common. However, it is currently fetching from hadoop-hdfs/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
