[MAPREDUCE-2483] Clean up duplication of dependent jar files

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.23.0
• Fix Version/s: 0.23.0
• Component/s: build
• Hadoop Flags: Reviewed
• Release Note: Removed duplicated hadoop-common library dependencies.
• Assignee: Eric Yang
• Reporter: Eric Yang
• Created: 11/May/11 18:15
• Updated: 15/Nov/11 00:49
• Resolved: 19/May/11 17:51

Description

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.

Issue Links

• blocks: HADOOP-6255 Create an rpm integration project
• incorporates: MAPREDUCE-2496 ivy: test conf should not extend common conf
• relates to: HADOOP-7289 ivy: test conf should not extend common conf