[jira] [Commented] (KAFKA-3717) On 0.10.0 branch, building javadoc results in very small subset of expected javadocs

["Grant Henke (JIRA)" <ji...@apache.org>]

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

Grant Henke commented on KAFKA-3717:
------------------------------------

Currently the build places a javadoc directory and jar in each modules build directory. This means you need to manually grab or merge all of them. I confirmed with [~gwenshap] that this was good enough for the 0.10 release. 

Going forward it would be nice to aggregate the docs output for all sub-modules. This is related to the work tracked by KAFKA-3405.  

Since manually collecting the javadocs works for now, I will update the title to track aggregating javadocs. 

> On 0.10.0 branch, building javadoc results in very small subset of expected javadocs
> ------------------------------------------------------------------------------------
>
>                 Key: KAFKA-3717
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3717
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Gwen Shapira
>            Assignee: Grant Henke
>
> If you run "./gradlew javadoc", you will only get JavaDoc for the High Level Consumer. All the new clients are missing.
> See here: http://home.apache.org/~gwenshap/0.10.0.0-rc5/javadoc/
> I suggest fixing in 0.10.0 branch and in trunk, not rolling a new release candidate, but updating our docs site.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)