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

Michael Dürig edited comment on OAK-301 at 8/5/13 3:12 PM:
-----------------------------------------------------------

Starting from revision 1510533 javadoc will per default not be included any 
more in the default site build. For the time being I added the 
{{site-with-javadoc}} profile to add javadoc to the site build. We can refine 
revisit/refine this further once we look at how to handle documentation across 
releases. 

I updated [above instructions | 
https://issues.apache.org/jira/browse/OAK-301?focusedCommentId=13726407&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13726407]
 accordingly. 
                
      was (Author: mduerig):
    Starting from revision 1510531 javadoc will per default not be included any 
more in the default site build. For the time being I added the 
{{site-with-javadoc}} profile to add javadoc to the site build. We can refine 
revisit/refine this further once we look at how to handle documentation across 
releases. 

I updated [above instructions | 
https://issues.apache.org/jira/browse/OAK-301?focusedCommentId=13726407&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13726407]
 accordingly. 
                  
> Document Oak
> ------------
>
>                 Key: OAK-301
>                 URL: https://issues.apache.org/jira/browse/OAK-301
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: doc
>            Reporter: Jukka Zitting
>
> To make it easier for new people to get involved, we should have some higher 
> level documentation than just javadocs and dev@ threads about key parts of 
> the internal design in Oak.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to