hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-6671) To use maven for hadoop common builds
Date Tue, 19 Jan 2016 13:48:40 GMT

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

ASF GitHub Bot commented on HADOOP-6671:
----------------------------------------

GitHub user make5020 opened a pull request:

    https://github.com/apache/hadoop/pull/69

    Creating updated branch for Hadoop-6671

    git-svn-id: https://svn.apache.org/repos/asf/hadoop/common/branches/HADOOP-6671-2@956573
13f79535-47bb-0310-9956-ffa450edef68

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/hadoop HADOOP-6671-2

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hadoop/pull/69.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #69
    
----
commit 3415f9569cce3d5811e95dba2ce21682d8b485f2
Author: Giridharan Kesavan <gkesavan@apache.org>
Date:   2010-06-21T13:20:01Z

    Creating updated branch for Hadoop-6671
    
    git-svn-id: https://svn.apache.org/repos/asf/hadoop/common/branches/HADOOP-6671-2@956573
13f79535-47bb-0310-9956-ffa450edef68

----


> 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
>             Fix For: 0.23.0
>
>         Attachments: HADOOP-6671-AA.patch, HADOOP-6671-AB.patch, HADOOP-6671-AC.patch,
HADOOP-6671-AC.sh, HADOOP-6671-AD.patch, HADOOP-6671-AD.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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message