nar-javah requires the 'compile' dependency resolution

Newer javah errors out when it encounters references to classes that are
not on the class path. Therefore we need to make sure that the
'-classpath' argument is fully populated.

Reported by Tobias Pietzsch.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Add a unit test to ensure that javah finds all required dependencies

It appears that javah is no longer content without having all the
referred classes on the class path since Java 7. In other words, when a
class with a native method refers to a class outside the current class
path, javah now complains loudly and errors out.

Adapt the it0003/it0004 combo to test that javah finds all the classes
it requires.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Merge remote-tracking branch 'origin/javah-dependencies'

This topic branch fixes nar-javah for Java 7's javah which requires all
compile-scope dependencies to be listed even on javah's class path.

The problem was reported several times, latest by Tobias Pietzsch who
also provided the initial version of the integration test demonstrating
the problem.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>