[
https://issues.apache.org/jira/browse/JCLOUDS-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984493#comment-13984493
]
Andrew Phillips commented on JCLOUDS-147:
-----------------------------------------
> We definitely do want Javadocs for all the released repos i.e., jclouds,
> karaf, -chef, -labs, -cli,
> and the -labs* merged into a single Javadoc site.
If we have the code in separate repos, and separate deliverables from the ASF,
are you sure we want merged documentation? As a developer, I would then also
suspect all these classes to be available in e.g. jclouds-all, which they're
not.
> 2) Create a gh-pages repo at github.com/jclouds/javadoc, host it there, and
> do an
> IFRAME on jclouds.apache.org
We did this originally, but gh-pages has trouble as the repos start getting
huge - stuff starts falling over.
How about Cloud Files, or some other blobstore. Would that be a potential
option?
> 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)
