Java 7 gives a nicer javadocs look and feel (less Geocities-like).
So you can optionally generate these nicer javadocs for the website without screwing anything else up, if you have the urge. The trick is you must use java7, but also have the minimal compiler version (e.g. java6 or whatever) so you can set your bootclasspath to its rt.jar (Apple's Java5 and Java6 JDKs call this file Classes/classes.jar instead - substitute in the cmdlines given below). This way the javadocs won't include any bogus java7 interfaces like AutoCloseable that don't actually apply.
In order to produce all of the documentation for a release, including a top level index, javadocs, changes, etc., use ant documentation under both lucene/ and solr/.
- When making the actual release, please always use the actual minimum compiler version!!!!
E.g. if its java5, put an actually java5 compiler in your JAVA_HOME and then put $JAVA_HOME/bin in the front of your path. Although it might be safe to do otherwise, just do this and you don't need to worry.
- To make java7 javadocs for the website, first take your checkout of the release tag and clean old docs:
rm -rf solr/build/docs lucene/build/docs
- Next put a java7 compiler in your JAVA_HOME and $JAVA_HOME/bin in the front of your path.
Under lucene/: ant -Dversion=X.Y.Z -Djavadoc.noindex=false -Dbootclasspath=/path/to/the/minimum/java/jre/lib/rt.jar documentation
Under solr/: ant -Dversion=X.Y.Z -Djavadoc.noindex=false -Dspecversion=X.Y.Z -Dbootclasspath=/path/to/the/minimum/java/jre/lib/rt.jar documentation
- Now you have fancy javadocs under lucene/build/docs/api and solr/build/docs/api, that otherwise link to the correct java versions and APIs, just look (hopefully) nicer.
- Deploy these to the website instead of the ones from the RC. (someone could always volunteer to do that after the release really at any time)