Return-Path: X-Original-To: apmail-giraph-dev-archive@www.apache.org Delivered-To: apmail-giraph-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4231FDD11 for ; Tue, 30 Oct 2012 19:14:15 +0000 (UTC) Received: (qmail 34521 invoked by uid 500); 30 Oct 2012 19:14:13 -0000 Delivered-To: apmail-giraph-dev-archive@giraph.apache.org Received: (qmail 34425 invoked by uid 500); 30 Oct 2012 19:14:13 -0000 Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@giraph.apache.org Delivered-To: mailing list dev@giraph.apache.org Received: (qmail 34257 invoked by uid 500); 30 Oct 2012 19:14:13 -0000 Delivered-To: apmail-incubator-giraph-dev@incubator.apache.org Received: (qmail 34239 invoked by uid 99); 30 Oct 2012 19:14:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Oct 2012 19:14:13 +0000 Date: Tue, 30 Oct 2012 19:14:13 +0000 (UTC) From: "Roman Shaposhnik (JIRA)" To: giraph-dev@incubator.apache.org Message-ID: <1249025049.46302.1351624453442.JavaMail.jiratomcat@arcas> In-Reply-To: <990376579.45276.1351616414793.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (GIRAPH-392) Can't build hadoop 0.23+ profiles 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/GIRAPH-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487139#comment-13487139 ] Roman Shaposhnik commented on GIRAPH-392: ----------------------------------------- One option is to disable giraph-formats-contrib altogether for new Hadoop profiles (we can't make accumulo work anyway since the upstream accumulo only supports 0.20.205). However, it looks like making hcatalog work shouldn't be that difficult and that leaves us with HBase. On one hand, it shouldn't be that difficult to make it work, but that would require a workaround of an HBase artifacts built against particular Hadoop ones available in local maven cache. What would be the preferred way of moving forward here? > Can't build hadoop 0.23+ profiles > --------------------------------- > > Key: GIRAPH-392 > URL: https://issues.apache.org/jira/browse/GIRAPH-392 > Project: Giraph > Issue Type: Bug > Components: build > Affects Versions: 0.2.0 > Reporter: Roman Shaposhnik > Assignee: Roman Shaposhnik > Priority: Blocker > Fix For: 0.2.0 > > > {noformat} > $ mvn -Phadoop_2.0.2 -DskipTests clean install > ...... > [WARNING] The POM for org.apache.hadoop:hadoop-core:jar:0.20.1 is missing, no dependency information available > [WARNING] The POM for org.apache.hadoop:hadoop-test:jar:2.0.2-alpha is missing, no dependency information available > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Apache Giraph Parent .............................. SUCCESS [0.446s] > [INFO] Apache Giraph ..................................... SUCCESS [1:00.793s] > [INFO] Apache Giraph Formats ............................. FAILURE [0.509s] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 1:01.960s > [INFO] Finished at: Tue Oct 30 09:59:01 PDT 2012 > [INFO] Final Memory: 69M/719M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project giraph-formats-contrib: Could not resolve dependencies for project org.apache.giraph:giraph-formats-contrib:jar:0.2-SNAPSHOT: Failure to find org.apache.hadoop:hadoop-test:jar:2.0.2-alpha in http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn -rf :giraph-formats-contrib > {noformat} -- 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