[
https://issues.apache.org/jira/browse/JCLOUDS-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984460#comment-13984460
]
Everett Toews commented on JCLOUDS-147:
---------------------------------------
I'm only interested in the Javadocs for the website, which is to say, our users
are only interested in the Javadocs. No need for all of that other Maven site
stuff on jclouds.apache.org.
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.
I don't think we want another GitHub account for this. We've lived without
properly hosted Javadoc for this long. The fix we make should be the permanent
fix.
What are the options?
1) Host it in svn and viewable on jclouds.apache.org/reference/javadoc/1.7.1,
jclouds.apache.org/reference/javadoc/1.7.2, etc.
This will take a lot of storage over time. Can svn handle it?
2) Create a gh-pages repo at github.com/jclouds/javadoc, host it there, and do
an IFRAME on jclouds.apache.org
What else?
> 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)
