jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Phillips <notificati...@github.com>
Subject Re: [jclouds-site] Release 1.7.3 (#104)
Date Mon, 02 Jun 2014 11:47:55 GMT
> Did someone ever put a call out on the Apache general list to find out how other project's
solved their Javadoc hosting?

@everett-toews We forwarded it on to `infrastructure@`, yes. The thread is called "Re: Javadoc
hosting for ASF projects (question from jclouds)?", but for some reason I can't seem to find
it in the infra archives ;-(

The responses were:
```
What about doing this via available maven repos in a generic way?

Most projects do already deploy javadoc to maven.
A central script could gather all javadoc.jar maven artifacts from ASF identified with 
GroupId org.apache.* and publish them on http://javadoc.apache.org/$ArtifactId ?

just an idea...
```
this:
```
One alternative is to use svnpubsub with the SCM Publish plugin [1]. Your site probably already
uses svnpubsub (perhaps under the covers using the CMS).

This will be immediately reflected onto the site and browse properly.

To make the size most efficient, I've found it helpful to disable timestamps in the javadoc
generation so there are only material differences published:

<notimestamp>true</notimestamp>

We also publish to the same location each time (say /apidocs/latest/), then make an SVN copy
to version it (an example of this for some other Maven generated documentation is at [2]).
```
and a response to the latter
```
Yup but the issue is to run that from Jenkins which means storing svn credentials.
Perso I use this but from my own Jenkins instance.
```

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/104#issuecomment-44827761
Mime
View raw message