Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D10F4200AE4 for ; Thu, 26 May 2016 02:07:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id CF79C160A2E; Thu, 26 May 2016 00:07:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 232CA160A29 for ; Thu, 26 May 2016 02:07:13 +0200 (CEST) Received: (qmail 24178 invoked by uid 500); 26 May 2016 00:07:13 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 24167 invoked by uid 99); 26 May 2016 00:07:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 May 2016 00:07:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id CCAE22C1F56 for ; Thu, 26 May 2016 00:07:12 +0000 (UTC) Date: Thu, 26 May 2016 00:07:12 +0000 (UTC) From: "Karthik Kambatla (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (YARN-5132) Exclude generated protobuf sources from YARN Javadoc build MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 26 May 2016 00:07:15 -0000 [ https://issues.apache.org/jira/browse/YARN-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301173#comment-15301173 ] Karthik Kambatla edited comment on YARN-5132 at 5/26/16 12:06 AM: ------------------------------------------------------------------ I see several reasons to get this in: # As Subru, Chris and others mentioned, I don't see why we should publish javadocs of these proto generated classes. We should actually update the release script to remove javadoc from proto files. [~vinodkv], [~leftnoteasy] - you have been working on the releases recently, do we publish javadocs for these? # All JIRAs see these javadoc errors. It is painstakingly hard to figure out what javadoc issues the patch introduces. was (Author: kasha): I see several reasons to get this in: # As Subru, Chris and others mentioned, I don't see why we should publish javadocs of these proto generated classes. We should actually update the release script to remove javadoc from proto files. [~vinodkv], [~leftnoteasy] - you have been working on the releases recently, do we publish javadocs for these? # All JIRAs see these javadoc errors. It is painstakingly hard to figure out what javadoc issues the patch introduces. The example I ran into YARN-5035. > Exclude generated protobuf sources from YARN Javadoc build > ---------------------------------------------------------- > > Key: YARN-5132 > URL: https://issues.apache.org/jira/browse/YARN-5132 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Subru Krishnan > Assignee: Subru Krishnan > Priority: Critical > Attachments: YARN-5132-v1.patch > > > Currently YARN build includes Javadoc from generated protobuf sources which is causing CI to fail. This JIRA proposes to exclude generated protobuf sources from YARN Javadoc build -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org