[daisy] [JIRA] Commented: (DSY-445) wrapper script issues

[Robert Kindl]

> The config file of the 1.5 release implements this behaviour. I changed it
in the 2.0 release because the windows installer of MySQL puts the java
command on the PATH by default, but it does not set the JAVA_HOME
environment variable. So I thought it would be less error prone to use the
java command, because this is usually on the PATH both on linux and windows
systems. I realized however, that many other tools, like the backup tool,
rely on JAVA_HOME also, so we probably could assume that it is set.

It depends.
The same is true for eg. Oracle client installation which also set PATH to
Java bundled with this client (version 1.4).

Obviously this v1.4 java.exe is not capable of running current Daisy
distribution.

In my case - I have side by side installation of  Oracle, MySQL, Daisy and
several Java versions.

So if I don't want to break anything it's best for me to use JAVA_HOME
environment variable for Daisy and PATH for Oracle client (or hardcode path
in wrapper scripts).

> Would be even better though if we had something like:
> set.default.JAVA_HOME=
> wrapper.java.command=%JAVA_HOME%java.exe
> meaning starting up with an empty JAVA_HOME that can be overriden from a
set environment variables. This does not work well with the /bin appendix
however, no idea how to get around that.

I agree with this idea - I already modified my script like this:

# Environment variables
set.default.DAISY_HOME=
set.default.DAISY_DATADIR=
set.default.JAVA_HOME=
set.MERLIN_HOME=%DAISY_HOME%/repository-server/merlin
set.WRAPPER_HOME=%DAISY_HOME%/wrapper

# Java Application
wrapper.java.command=%JAVA_HOME%/bin/java.exe

And it's working fine including /bin suffix

Rob