[
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067178#comment-13067178
]
Tom White commented on HADOOP-6671:
-----------------------------------
* On naming, I think the "hadoop-" prefix in module names is unnecessary. I
would prefer common/common-main, etc.
* I updated the pre-commit job for Maven to test that "bad" patch in
HADOOP-7413. See the end of
https://builds.apache.org/view/G-L/view/Hadoop/job/PreCommit-HADOOP-Build-maven/11/console.
The only missing -1 is for the javadoc, which failed due to missing artifacts
and can be fixed by adding a line calling "mvn install -DskipTests" in the
section labelled "Pre-build trunk to verify trunk stability and javac warnings".
* We need to make sure that cross project builds still work. When I tried doing
"mvn install", then building HDFS I got an error which can be fixed with
HADOOP-6671-cross-project-HDFS.patch, which I posted a while back. We should
commit this, and do the same for MapReduce.
* Have you checked that you can run Hadoop from a tarball built using Maven?
(BTW https://builds.apache.org/job/Hadoop-Common-trunk-maven/ is building
nightly tarballs using Maven.)
* What needs doing to make for a smooth switchover as smooth for developers? We
should update http://wiki.apache.org/hadoop/HowToContribute (perhaps make a
copy so it's available before the switch). Anything else?
> To use maven for hadoop common builds
> -------------------------------------
>
> Key: HADOOP-6671
> URL: https://issues.apache.org/jira/browse/HADOOP-6671
> Project: Hadoop Common
> Issue Type: Sub-task
> 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-f.patch, HADOOP-6671-g.patch,
> HADOOP-6671-h.patch, HADOOP-6671-i.patch, HADOOP-6671-j.patch,
> HADOOP-6671-k.sh, HADOOP-6671-l.patch, HADOOP-6671-m.patch,
> HADOOP-6671-n.patch, HADOOP-6671-o.patch, HADOOP-6671-p.patch,
> HADOOP-6671-q.patch, HADOOP-6671.patch, HADOOP-6671b.patch,
> HADOOP-6671c.patch, HADOOP-6671d.patch, build.png, common-mvn-layout-i.sh,
> hadoop-commons-maven.patch, mvn-layout-e.sh, mvn-layout-f.sh,
> mvn-layout-k.sh, mvn-layout-l.sh, mvn-layout-m.sh, mvn-layout-n.sh,
> mvn-layout-o.sh, mvn-layout-p.sh, mvn-layout-q.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
