hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-6671) To use maven for hadoop common builds
Date Fri, 29 Jul 2011 17:34:16 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072935#comment-13072935
] 

Tom White commented on HADOOP-6671:
-----------------------------------

There's a small issue with moving hadoop-common/src/test/bin to dev-support since it is used
as an svn:externals definition from HDFS and MapReduce. I suggest that we leave the bin directory
there as well as creating the new dev-support directory, since the test-patch.sh script has
been modified to work for Maven, so we need both. When all three projects have been Mavenized
then we'll be able to remove the bin directory completely (and the svn:externals).

> 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-AA.patch, HADOOP-6671-AB.patch, HADOOP-6671-AC.patch,
HADOOP-6671-AC.sh, 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-AA.sh, mvn-layout-AB.sh,
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

        

Mime
View raw message