Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A3AC7DD81 for ; Thu, 25 Oct 2012 21:15:14 +0000 (UTC) Received: (qmail 50790 invoked by uid 500); 25 Oct 2012 21:15:14 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 50756 invoked by uid 500); 25 Oct 2012 21:15:14 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 50745 invoked by uid 99); 25 Oct 2012 21:15:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Oct 2012 21:15:14 +0000 Date: Thu, 25 Oct 2012 21:15:14 +0000 (UTC) From: "Alejandro Abdelnur (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1773495223.29447.1351199714309.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (HADOOP-6671) To use maven for hadoop common builds MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484486#comment-13484486 ] Alejandro Abdelnur commented on HADOOP-6671: -------------------------------------------- Nicholas, definitely it is, I guess it may have been while doing F&R of some testcases paths. > 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: build.png, common-mvn-layout-i.sh, 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-6671b.patch, HADOOP-6671c.patch, HADOOP-6671-cross-project-HDFS.patch, HADOOP-6671d.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.patch, HADOOP-6671-p.patch, HADOOP-6671-q.patch, hadoop-commons-maven.patch, mvn-layout2.sh, mvn-layout2.sh, 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 > > > 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. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira