[
https://issues.apache.org/jira/browse/JCLOUDS-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693032#comment-13693032
]
Andrew Phillips commented on JCLOUDS-147:
-----------------------------------------
Couple of questions to start with:
* are we interested in any elements of the Maven site other than the Javadocs
(e.g. FindBugs, RAT report)?
* if we're only interested in Javadocs, do we want them for individual projects
or are we only looking for the aggregate Javadocs?
The reason I'm asking is that, if it's the latter option, we can go for
something like
https://jclouds.ci.cloudbees.com/view/docs/job/jclouds-aggregate-javadocs/ and
ignore the Maven site generation entirely for now.
> Transfer jclouds API docs site and generation process to
> jclouds.incubator.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 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
