[
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000491#comment-13000491
]
Luke Lu commented on HADOOP-6671:
---------------------------------
Since HADOOP-7106 is moving forward, we should consider converting the all the
Hadoop core projects (common, hdfs, mapreduce) into one single multi-module
maven (2+) project. We can then easily do mvn install on the top-level and test
patches across the modules, or work in the module directory independently. This
has many advantages over a bunch of disjoint ant/ivy projects. Though maven2+
still has its issues, most can be resolved by using the right versions of
plugins. Our recent effort with a major multi-module maven project worked out
better than I expected. The more I worked with both maven (2+) and ant/ivy the
more I prefer maven to ant/ivy (mostly for much less ways to shoot myself in
the foot :)
> To use maven for hadoop common builds
> -------------------------------------
>
> Key: HADOOP-6671
> URL: https://issues.apache.org/jira/browse/HADOOP-6671
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.22.0
> Reporter: Giridharan Kesavan
> Attachments: build.png
>
>
> 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.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
