If batik is built before fop, fop's lib dependency on batik
will overwrite the patched batik jar.
There was a previous commit that attempts to deal with the issue,
but it created dependency not found problem when
fop is the only one built.
This commit properly deals with the issue by renaming the
batik jar that fop depends on, thus not overwriting the patched
batik benchmark.

Fop carries a batik-all-1.9.jar with it, which will overwrite the batik benchmark jar
when unzipped into scratch directory, rendering the patch to batik 1.9 ineffective.
Fop benchmark doesn't seem to actually use the jar. So removing it from the list of
jars to include in fop doesn't affect running fop benchmark, and batik is now fine.

lusearch-fix was added in the last release due to a bug in the old
version of lucene. This bug is fixed in the newer version, thus
there is no need for lusearch-fix benchmark anymore.

also remove obsolete Tomcat patches

Version bump lusearch

See merge request !9

Still use latest documentation

There is a problem with classpath such that javadoc wasn't able to find
`commons.cli` package;
There are also small problems with using angle brackets `<` & `>` that
caused javadoc to complain 'malformed HTML tag'.

After this fix, the remaining errors are all about `@date` and `@id`
tags. These are not supported by javadoc. However they don't pose a
problem to the generated HTML document. So these problems are ignored
for now.

PMD: remove JDK 7 requirement walk-around in toolchain.xml generation; add script to ant source target