You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2016/03/18 00:17:33 UTC

[jira] [Commented] (CALCITE-1160) Avatica javadoc

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

Julian Hyde commented on CALCITE-1160:
--------------------------------------

Other site issues:
* There's no favicon for http://calcite.apache.org/avatica/
* Community page is a mess. Obsolete it and link Calcite's?
* There should be a link from Avatica site to Calcite but there is currently not
* Develop page is a mess, a mixture of Calcite and Avatica.


> Avatica javadoc
> ---------------
>
>                 Key: CALCITE-1160
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1160
>             Project: Calcite
>          Issue Type: Bug
>          Components: avatica, site
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>
> Figure out how we want to publish Avatica javadoc.
> Right now the javadoc points to the javadoc that was generated in the previous calcite release. When I generate javadoc for calcite 1.7 the contents will no longer include avatica packages. The javadoc for each package will still be there in the web site until I explicitly delete it.
> * Should http://calcite.apache.org/avatica/docs/ have "api" and "test api" links?
> * Should avatica javadoc be separate from calcite javadoc?
> * Make calcite javadoc reference avatica javadoc (i.e. uses of avatica classes should be hyperlinks)
> * Document a process to re-generate avatica javadoc as part of an avatica release



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