[
https://issues.apache.org/jira/browse/KAFKA-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15031149#comment-15031149
]
ASF GitHub Bot commented on KAFKA-2906:
---------------------------------------
GitHub user ewencp opened a pull request:
https://github.com/apache/kafka/pull/599
KAFKA-2906: Fix Connect javadocs, restrict only to api subproject, and
clean up javadoc warnings.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ewencp/kafka kafka-2906-connect-javadocs
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/599.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #599
----
commit 1568235f9a8e9b986b5ef36f23ecd956f341d206
Author: Ewen Cheslack-Postava <m...@ewencp.org>
Date: 2015-11-29T19:40:13Z
KAFKA-2906: Fix Connect javadocs, restrict only to api subproject, and
clean up javadoc warnings.
----
> Kafka Connect javadocs not built properly
> -----------------------------------------
>
> Key: KAFKA-2906
> URL: https://issues.apache.org/jira/browse/KAFKA-2906
> Project: Kafka
> Issue Type: Bug
> Components: copycat
> Affects Versions: 0.9.0.0
> Reporter: Ewen Cheslack-Postava
> Assignee: Ewen Cheslack-Postava
>
> It looks like the filters used in other projects aren't working properly for
> the nested connect projects, resulting in javadocs not being generated.
> We also probably only want the javadocs for connect:api to be generated. The
> rest of the packages are all private implementation and any docs are better
> handled in the regular docs instead of as javadocs (e.g. config options).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
