Publish versioned javadocs & remove head javadocs from repo

[joelittlejohn]

Original author: joelittl...@gmail.com (December 23, 2010 00:34:19)

Problem:

Generating apidocs into the main repo like:

https://jsonschema2pojo.googlecode.com/hg/apidocs/

is generally an annoyance, causing additional noise in changesets and more regular conflicts when merging. The latest dev docs are also (arguably) not that useful.

Solution:

Publish javadocs for releases into the wiki repo as per:
http://littleware.blogspot.com/2009/11/publish-javadoc-to-google-code-via.html

(hopefully in an automated, or at least scripted way :D)

Original issue: http://code.google.com/p/jsonschema2pojo/issues/detail?id=6

[joelittlejohn]

From joelittl...@gmail.com on December 23, 2010 13:13:25
Having javadocs in the main repo also messes up the ohloh stats:
https://www.ohloh.net/p/jsonschema2pojo/analyses/latest

[joelittlejohn]

From joelittl...@gmail.com on January 25, 2011 21:14:59
head javadocs removed from trunk (& link removed from the homepage). ohloh stats are looking more sensible now.

need to start pushing javadocs for specific versions into the wiki repo.

[joelittlejohn]

From joelittl...@gmail.com on February 06, 2011 23:39:22
Fixed.

http://wiki.jsonschema2pojo.googlecode.com/hg/javadocs/0.1.5/index.html