Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Wed, 14 Oct 2015 22:30:05 +0000 (UTC)
From: "Chris Nauroth (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12905035.1444861781000.42508.1444861805900@Atlassian.JIRA>
In-Reply-To: <JIRA.12905035.1444861781000@Atlassian.JIRA>
References: <JIRA.12905035.1444861781000@Atlassian.JIRA>
 <JIRA.12905035.1444861781636@arcas>
Subject: [jira] [Created] (HADOOP-12479) ProtocMojo does not log the reason
 for a protoc compilation failure.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Chris Nauroth created HADOOP-12479:
--------------------------------------

             Summary: ProtocMojo does not log the reason for a protoc compilation failure.
                 Key: HADOOP-12479
                 URL: https://issues.apache.org/jira/browse/HADOOP-12479
             Project: Hadoop Common
          Issue Type: Bug
          Components: build
            Reporter: Chris Nauroth
            Assignee: Chris Nauroth
            Priority: Minor


If protoc fails with a compilation error in the proto files, our Maven plugin won't print the details.  The only way to figure it out is to repeat running the {{protoc}} command manually from outside the Hadoop build.  This is because our {{ProtocMojo}} only captures stdout from the {{protoc}} command, and compilation errors get written to {{stderr}}.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)