[
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064278#comment-13064278
]
Alejandro Abdelnur commented on HADOOP-6671:
--------------------------------------------
Thanks for trying it out Giri.
#1 - I'm thinking, that even if it will be verbose, the module dir names should
match the module artifact name. It seems more intuitive to me, then it would be
as my second diagram in my previous comment.
#2 - My idea is to use trunk/hadoop-root/pom.xml. I've run into problems in the
past with some plugins when using as parent the same POM used by the reactor.
Some plugins break unless the root-reactor pom is installed in .m2 cache.
#3 - the problem here is that the reactor is not including the doclet module
and you don't have the doclet artifact in your .m2 cache. Run 'mvn install'
from trunk once, then you can work in a sub-module an the no-reactor modules
will be picked up from .m2 cache.
Common depends on doclet as provided for javadocs/jdiff runs. Doing what is
mentioned in #3 will take care of this.
Note that once this is committed, nightly builds would push all module
artifacts to the Maven snapshots repo and you'll be able to work from any
module consuming the latest nightly artifacts (that are not resolved by the
reactor).
> 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.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.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
