Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-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 86AE0DA3A for ; Thu, 28 Feb 2013 12:01:22 +0000 (UTC) Received: (qmail 43633 invoked by uid 500); 28 Feb 2013 12:01:20 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 42626 invoked by uid 500); 28 Feb 2013 12:01:18 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 42524 invoked by uid 99); 28 Feb 2013 12:01:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2013 12:01:17 +0000 Date: Thu, 28 Feb 2013 12:01:17 +0000 (UTC) From: "Harsh J (JIRA)" To: common-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HADOOP-9346) Upgrading to protoc 2.5.0 fails the build MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Harsh J created HADOOP-9346: ------------------------------- Summary: Upgrading to protoc 2.5.0 fails the build Key: HADOOP-9346 URL: https://issues.apache.org/jira/browse/HADOOP-9346 Project: Hadoop Common Issue Type: Task Reporter: Harsh J Priority: Minor Reported over the impala lists, one of the errors received is: {code} src/hadoop-common-project/hadoop-common/target/generated-sources/java/org/a= pache/hadoop/ha/proto/ZKFCProtocolProtos.java:[104,37] can not find symbol. symbol=EF=BC=9A class Parser location=EF=BC=9A package com.google.protobuf {code} Worth looking into as we'll eventually someday bump our protobuf deps. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira