[ 
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Abdelnur updated HADOOP-6671:
---------------------------------------

    Attachment: HADOOP-6671-AC.sh
                HADOOP-6671-AC.patch

Attached patch integrates Eric's suggestions:

* Using the package phase with a profile to create the TAR.

* There are 2 TAR profiles, one is 'tar' the other is 'bintar'. '-Ptar' does 
the same TAR 'ant tar' and '-Pbintar' does the same TAR 'ant binary' does.

* 'mvn install/deploy' pushes 4 JARs: hadoop-common, hadoop-common-tests, 
hadoop-common-sources and hadoop-common-test-sources.

* The 'dev' dir has been renamed to 'dev-support'


At this point all feedback has been integrated into the patch. Rebasing 
requires constant manual resolutions because this patch touches the layout.

It would be great if we get this committed (for developers is working and also 
there is a patch for HDFS ant build that make HDFS ant build work with 
Mavenized common).

I'm currently working HDFS mavenization and I should have a first drop later 
today.


> 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

        

Reply via email to