Version builds should automatically update Javadoc in subversion

[GoogleCodeExporter]

We should come up with a script or ant section or some other simple way of 
doing all the steps necessary to update the javadoc when a new version is 
released.

Copying over the current manual steps to do that from issue 32:
* generate the javadoc in the trunk inside ./doc
* svn rm ../javadoc/latest-stable/*
* svn ci ../javadoc/latest-stable
* cp -r doc/* ../javadoc/latest-stable
* svn add ../javadoc/latest-stable/*
* set the svn:mime-type property on all .html files in the repository to 
text/html 

Not sure if this is the easiest way to do that, if not, please comment on this 
issue.

I could come up with a bash script that does that easily, but are builders 
using linux/unix?

Original issue reported on code.google.com by johann.petrak@gmail.com on 9 Dec 2010 at 2:06

[GoogleCodeExporter]

(Oops, I though I'd replied to this earlier ... note to self, "hitting" reply 
in email doesn't seem to update the bug. Apologies.)

As far as I know, all our developers have access to some bash-compatible 
system, so it's fine to assume that bash scripts work for releases. There are 
likely to be even fewer release engineers than general contributors anyway, so 
I don't think we need to be very general here.

Original comment by widd...@google.com on 13 Dec 2010 at 5:23

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I have checked in the script update-release-docs.sh which should do this. It 
has to be run from the trunk root directory. This script so far assumes that 
every step will work fine (no error checking is done).

Original comment by johann.petrak@gmail.com on 13 Dec 2010 at 10:29

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****