Have javadocs built automagically; published in a consistent public location about fenzo HOT 1 CLOSED

Javadocs now hosted on netflix.github.io. It's still worth investigating whether there's a way to better-automate how the javadocs update and deploy... it's a clumsy hand-cranked procedure now:

• Build the javadocs in the main Fenzo/ directory (where GitHub stores the root of the Fenzo project) with ./gradlew javadoc

• Create a directory parallel to the main Fenzo/ directory called FenzoJavadocs/

• Run the following script to copy the javadocs over to that directory:

  cp -R Fenzo/fenzo-core/build/docs/javadoc/ FenzoJavadocs/fenzo-core/
cp -R Fenzo/fenzo-triggers/build/docs/javadoc/ FenzoJavadocs/fenzo-triggers/

• Switch over to the gh-pages branch in GitHub.

• (Recursively) copy the contents of FenzoJavadocs/ into the main Fenzo/ directory

• Commit+push this to the gh-pages branch.

from fenzo.