-
Notifications
You must be signed in to change notification settings - Fork 28.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MINOR][BUILD] Update genjavadoc to 0.13 #24443
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM if it passes
Test build #104833 has finished for PR 24443 at commit
|
Argh .. |
(I assume it won't work until your other change is in.) |
Thanks for the investigation! |
Test build #104840 has finished for PR 24443 at commit
|
Uh ok that's bad news. Genjavadoc update may not fly |
Test build #104843 has finished for PR 24443 at commit
|
OK, that worked. I think the new genjavadoc fixes some spurious warnings but uncovers some more, but then I just worked around them in the docs. |
LGTM Merged to master. |
…er upgrading genjavadoc to 0.14 ### What changes were proposed in this pull request? This PR backport #24443 to fix java doc generation after upgrading genjavadoc to 0.14. ### Why are the changes needed? Fix javadoc generation issue. ### Does this PR introduce any user-facing change? No. ### How was this patch tested? ``` ./build/sbt -Phadoop-2.7 -Pkubernetes -Phive-thriftserver -Pkinesis-asl -Pyarn -Pspark-ganglia-lgpl -Phive -Pmesos clean test:package streaming-kinesis-asl-assembly/assembly ./build/sbt -Phadoop-2.7 -Pkubernetes -Phive-thriftserver -Pkinesis-asl -Pyarn -Pspark-ganglia-lgpl -Phive -Pmesos unidoc ``` Closes #25841 from wangyum/genjavadoc-0.13-branch-2.4. Authored-by: Yuming Wang <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
What changes were proposed in this pull request?
Kind of related to gatorsmile#5 - let's update genjavadoc to see if it generates fewer spurious javadoc errors to begin with.
How was this patch tested?
Existing docs build