[
https://issues.apache.org/jira/browse/JCLOUDS-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989176#comment-13989176
]
Andrew Phillips commented on JCLOUDS-147:
-----------------------------------------
> Merging the source trees before generating the Javadoc is much easier.
Agreed. Question is only: do we want to proceed with the existing PR until we
get round to doing this (we should be able to replace the "1.7.2/jclouds" and
"1.7.2/jclouds-labs-openstack" Javadocs with symlinks to the complete set)? Or
rather drop the PR and wait until we have this things sorted out?
> Transfer jclouds API docs site and generation process to jclouds.apache.org
> ---------------------------------------------------------------------------
>
> Key: JCLOUDS-147
> URL: https://issues.apache.org/jira/browse/JCLOUDS-147
> Project: jclouds
> Issue Type: Task
> Components: docs
> Reporter: Andrew Bayer
> Assignee: Andrew Phillips
>
> We should fold the apidocs into the main jclouds site, and we should fold the
> apidocs site generation process into the release process (doc'd at
> https://wiki.apache.org/jclouds/Releasing%20jclouds).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
