From common-issues-return-7149-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org Fri Apr 02 20:27:50 2010 Return-Path: Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: (qmail 53987 invoked from network); 2 Apr 2010 20:27:50 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Apr 2010 20:27:50 -0000 Received: (qmail 61225 invoked by uid 500); 2 Apr 2010 20:27:50 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 61140 invoked by uid 500); 2 Apr 2010 20:27:50 -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 61132 invoked by uid 99); 2 Apr 2010 20:27:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Apr 2010 20:27:50 +0000 X-ASF-Spam-Status: No, hits=-1207.4 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Apr 2010 20:27:49 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id AA3A1234C4CB for ; Fri, 2 Apr 2010 20:27:28 +0000 (UTC) Message-ID: <945441826.665601270240048696.JavaMail.jira@brutus.apache.org> Date: Fri, 2 Apr 2010 20:27:28 +0000 (UTC) From: "E. Sammer (JIRA)" To: common-issues@hadoop.apache.org Subject: [jira] Commented: (HADOOP-6671) To use maven for hadoop common builds In-Reply-To: <859246128.630391270120227191.JavaMail.jira@brutus.apache.org> 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=12852939#action_12852939 ] E. Sammer commented on HADOOP-6671: ----------------------------------- So much of the build system today "acts as" maven it might as well be maven. Having some consistency in the way the individual projects are built would be extremely nice. Maven is as painful as every other build tool we've seen but at least its pain comes in a consistent, known, quantity. The tooling support tends to be better due to the predictable nature of the the build process. The surrounding infrastructure (such as Hudson) is already mvn aware. The main problem with mvn tends to be errant dependencies in poms but this can be avoided (see the SpringSource Ivy / Maven repositories for an example of *very* well maintained metadata - http://www.springsource.com/repository/app/). +1 > To use maven for hadoop common builds > ------------------------------------- > > Key: HADOOP-6671 > URL: https://issues.apache.org/jira/browse/HADOOP-6671 > Project: Hadoop Common > Issue Type: Improvement > Components: build > Affects Versions: 0.22.0 > Reporter: Giridharan Kesavan > > 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. - You can reply to this email to add a comment to the issue online.