[HADOOP-6671] To use maven for hadoop common builds

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.22.0
• Fix Version/s: 0.23.0
• Component/s: build
• Hadoop Flags: Reviewed
• Assignee: Alejandro Abdelnur
• Reporter: Giridharan Kesavan
• Created: 01/Apr/10 11:09
• Updated: 17/May/18 06:00
• Resolved: 02/Aug/11 20:48

Description

We are now able to publish hadoop artifacts to the maven repo successfully [ Hadoop-6382]
Drawbacks with the current approach:

• Use ivy for dependency management with ivy.xml
• Use maven-ant-task for artifact publishing to the maven repository
• pom files are not generated dynamically

To address this I propose we use maven to build hadoop-common, which would help us to manage dependencies, publish artifacts and have one single xml file(POM) for dependency management and artifact publishing.

I would like to have a branch created to work on mavenizing hadoop common.

Issue Links

• blocks: HDFS-2096 Mavenization of hadoop-hdfs
• is depended upon by: HADOOP-7481 Wire AOP test in Mavenized Hadoop common
• is depended upon by: HDFS-2196 Make ant build system work with hadoop-common JAR generated by Maven
• is depended upon by: MAPREDUCE-2741 Make ant build system work with hadoop-common JAR generated by Maven
• is related to: HADOOP-7501 publish Hadoop Common artifacts (post HADOOP-6671) to Apache SNAPSHOTs repo
• relates to: HADOOP-7528 Maven build fails in Windows
• relates to: HADOOP-6629 versions of dependencies should be specified in a single place
• relates to: HADOOP-7069 Replace forrest with supported framework
• relates to: HADOOP-6407 Have a way to automatically update Eclipse .classpath file when new libs are added to the classpath through Ivy
• links to: GitHub Pull Request #387