[
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-6671:
------------------------------
Attachment: HADOOP-6671-cross-project-HDFS.patch
I've set up a Jenkins job to build common artifacts using Maven:
https://builds.apache.org/job/Hadoop-Common-trunk-maven/.
It's building the same artifacts as
https://builds.apache.org/job/Hadoop-Common-trunk/, including documentation and
native libraries, and reports for compiler warnings, tests, FindBugs, and
Checkstyle. The only missing report is for Clover which needs adding to the
Maven build.
Currently two tests are failing
(https://builds.apache.org/job/Hadoop-Common-trunk-maven/8/) - I'm not sure
why, as they pass for me locally using Maven, and on Hudson using Ant.
I also tried a cross-project build using Maven for common and Ant for HDFS. I
needed the attached patch to get the HDFS build to work - these are changes
that are needed anyway that we were getting away with using Ivy. MapReduce will
need similar changes.
> 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
> Assignee: Alejandro Abdelnur
> Attachments: HADOOP-6671-cross-project-HDFS.patch,
> HADOOP-6671-e.patch, HADOOP-6671.patch, HADOOP-6671b.patch,
> HADOOP-6671c.patch, HADOOP-6671d.patch, build.png,
> hadoop-commons-maven.patch, mvn-layout-e.sh, mvn-layout.sh, mvn-layout.sh,
> mvn-layout2.sh, mvn-layout2.sh
>
>
> 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
