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

Arun Suresh edited comment on YARN-5132 at 5/25/16 2:22 AM:
------------------------------------------------------------

bq.  then that means that non-Java clients are basically screwed. It also makes 
the Go example by Hortonworks extremely problematic. 
[~aw], appoligize but I do NOT see the connection between generated java 
classes and go clients. A go client would generate its own go files from the 
protobuf and use it.


was (Author: asuresh):
bq.  then that means that non-Java clients are basically screwed. It also makes 
the Go example by Hortonworks extremely problematic. 
[~aw], appoligize but I do see the connection between generated java classes 
and go clients. A go client would generate its own go files from the protobuf 
and use it.

> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to