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

Mate Szalay-Beko commented on ZOOKEEPER-3792:
---------------------------------------------

>  I noticed when doing the 3.5.7 release, and manually corrected the links

I think your manual correction has been updated since then, as it doesn't work 
now: [https://zookeeper.apache.org/doc/r3.5.7/index.html]

 

> Anyway, we talked that probably jute api docs is not even necessary to link

yep, the Jute classes are auto-generated for our internal API, I don't see much 
value to publish javadoc for them.

 

[~tison] do you plan to work on the fix? (this is our current procedure to 
generate the website: [https://github.com/apache/zookeeper/tree/website] )

If you have no time for this right now, then do you mind if I take this over? 
(although I don't think this is very high priority, nobody asked for the 
javadocs, and we publish the source in maven central, so I think most of the 
developers use their IDE to read it)

> Reconcile document site in 3.5.7 & 3.6.0
> ----------------------------------------
>
>                 Key: ZOOKEEPER-3792
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3792
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 3.6.0, 3.5.7
>            Reporter: Zili Chen
>            Assignee: Zili Chen
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> After ZOOKEEPER-3369 we generate document in {{apidocs/}} instead of {{api/}} 
> before. Moreover, the document site cannot proper linked to apidocs in 
> 3.6.0(but in 3.5.7, thought it is wrong in {{website}} branch, it is manually 
> corrected in {{asf-site}} branch}}.
> I propose we generate single aggregated document and place it under {{api/}} 
> folder, as well as bumping website for the update.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to