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 24EE2CD85 for ; Mon, 17 Mar 2014 16:47:29 +0000 (UTC) Received: (qmail 21211 invoked by uid 500); 17 Mar 2014 16:47:28 -0000 Delivered-To: apmail-giraph-dev-archive@giraph.apache.org Received: (qmail 21187 invoked by uid 500); 17 Mar 2014 16:47:27 -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 Delivered-To: moderator for dev@giraph.apache.org Received: (qmail 17341 invoked by uid 99); 17 Mar 2014 16:45:03 -0000 From: cerquide To: dev@giraph.apache.org Reply-To: dev@giraph.apache.org Message-ID: Subject: [GitHub] giraph pull request: GIRAPH-864: Fixed compilation problem Content-Type: text/plain Date: Mon, 17 Mar 2014 16:45:03 +0000 (UTC) GitHub user cerquide opened a pull request: https://github.com/apache/giraph/pull/5 GIRAPH-864: Fixed compilation problem As reported https://issues.apache.org/jira/browse/GIRAPH-864 , compiling does not work right now. There is a small problem with file giraph-rexster/giraph-rexster-io/pom.xml. The following fix makes it work. You can merge this pull request into a Git repository by running: $ git pull https://github.com/cerquide/giraph trunk Alternatively you can review and apply these changes as the patch at: https://github.com/apache/giraph/pull/5.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 #5 ---- commit e84906ef43f4b85329a0c6327f7a2c4d68c6a3e5 Author: Jesus Cerquides Date: 2014-03-17T16:37:41Z Fixed compilation problem ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---