[
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064258#comment-13064258
]
Giridharan Kesavan commented on HADOOP-6671:
--------------------------------------------
thanks for the clarification Alejandro.
You are right; common is just a folder. I missed deleting it.
1) most of the projects that I ve seen uses this convention
{noformat}
common/pom.xml
---common-main/pom.xml
{noformat}
2) can trunk/pom.xml used for module dependencies b/w common,hdfs & mapreduce?
(just wondering about the reason for root/pom.xml)
3) cd trunk/common-main/common
mvn install - I get the following error
{noformat}
[WARNING] The POM for org.apache.hadoop:hadoop-doclet:jar:0.23.0-SNAPSHOT is
missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Hadoop Common .............................. FAILURE [0.446s]
[INFO] Apache Hadoop Common Docs ......................... SKIPPED
[INFO] Apache Hadoop Common Distro ....................... SKIPPED
[INFO] Apache Hadoop Common Main ......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.683s
[INFO] Finished at: Tue Jul 12 17:19:57 PDT 2011
[INFO] Final Memory: 4M/81M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project hadoop-common: Could not resolve
dependencies for project org.apache.hadoop:hadoop-common:jar:0.23.0-SNAPSHOT:
Could not find artifact org.apache.hadoop:hadoop-doclet:jar:0.23.0-SNAPSHOT ->
[Help 1]
{noformat}
Not sure why common depends on docklet;
common depends on docklet which is not yet build/installed and hence its
fails(scope is set to provided);
I'm still testing the patch...
> 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
