Non default JAVA_HOME makes wrapper fail

[ascheman]

If java is not on a default path (as set by /etc/default/login or other means), the wrapper fails since the executable cannot be found when doctoolchain is finally called.

The reason for this is the call to bash with the -l flag in line 37:

doctoolchain.github.io/dtcw

Line 237 in 068e50e

bash -cl "$command"

This causes bash to work as login shell and reset any environment variables to their login defaults.

[rdmueller]

ok, here is why i added the line

export JAVA_HOME=

to the dtcw. dtcw checks for the correct java version by trying to execute it. This mostly uses the java version which is found on the path. It seems that gradle preferes the java version configured in JAVA_HOME - so there are cases when there versions differ. Then dtcw might say the java version is ok, but gradle picks up a version too high.

But gradle uses the version on the path if JAVE_HOME is not set. So I thought it is a good idea to deactive it.

But it seems it wasn't. Let's remove the line again.

[rdmueller]

I think this is solved, isn't it?