hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5132) Exclude generated protobuf sources from YARN Javadoc build
Date Thu, 26 May 2016 00:05:12 GMT

    [ https://issues.apache.org/jira/browse/YARN-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301173#comment-15301173

Karthik Kambatla commented on YARN-5132:

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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message