[
https://issues.apache.org/jira/browse/YARN-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300822#comment-15300822
]
Chris Douglas commented on YARN-5132:
-------------------------------------
>From the bug [~subru] cited, it looks like there's no solution for the javadoc
>warnings in 2.5, a version we're unlikely to change and Google is unlikely to
>fix.
[~aw], I think your point is that Jenkins should stop complaining about (new)
javadoc warnings in generated code, rather than giving up generating javadoc
entirely. The protobuf classes are public APIs, but they're not user-facing in
our Java APIs... I'm pretty ambivalent about keeping javadoc for them;
including it may mislead someone into writing against them, rather than the API
classes. Since (IIRC) we exclude other \@Private APIs from the generated
javadoc, this seems like a good change, overall. Unless there's a better way to
effect 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: [email protected]
For additional commands, e-mail: [email protected]
