This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Problem using $E(JAVA_HOME)
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 07, 2006
08:23 AM
Problem using $E(JAVA_HOME)
hello Everbyody,
I have multiple installation of java on my computer (jdk1.3,1.4,1.5) and JAVA_HOME is set to jdk1.3.
I have checked this with "echo %JAVA_HOME%" in windows console.
But if I use $E(JAVA_HOME) I returned a path to another jdk installation.
Whats joing wrong ?
Timo
I have multiple installation of java on my computer (jdk1.3,1.4,1.5) and JAVA_HOME is set to jdk1.3.
I have checked this with "echo %JAVA_HOME%" in windows console.
But if I use $E(JAVA_HOME) I returned a path to another jdk installation.
Whats joing wrong ?
Timo
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 14, 2006
01:30 PM
I assume that we are talking about an installer built as a launcher distribution (otherwise, if you run the installer jar file with a command similar to "java -cp my_setup.jar run", check the PATH variable or use an explicit c:\jdk1.5\jre\bin\java or something like that command).
Most likely, the installer you built has its own java search process defined in the JVM Resolution section of the Additional Tools view. The JVM Search instructions in that section, or the contents of a "jvm" file (no extension) stored in a Bundled JVM points the installer to a JRE on your system. The installer launcher may be pointed to a specific java home with -is:javahome command line parameter, but the use of that parameter is limited to JRE hints (search path instructions) defined in a bundled jre or jre search instructions. Basically, if the installer launcher has no record of a JRE installed "z:\MyJunk\jre\bin\java", there is no way to force that installer launcher to use that jre.
A bundled JVM is a self-extracting zip file for a platform it's defined. It should uncompress the contents to a current directory if you run that file (on a system it was created for). Once a bundled jvm is uncompressed, look for "jvm" file in the current directory and inspect the contents for JRE search instructions.
You may search support.installshield.com for the jvm file format and a custom jre bundling instructions.
Most likely, the installer you built has its own java search process defined in the JVM Resolution section of the Additional Tools view. The JVM Search instructions in that section, or the contents of a "jvm" file (no extension) stored in a Bundled JVM points the installer to a JRE on your system. The installer launcher may be pointed to a specific java home with -is:javahome command line parameter, but the use of that parameter is limited to JRE hints (search path instructions) defined in a bundled jre or jre search instructions. Basically, if the installer launcher has no record of a JRE installed "z:\MyJunk\jre\bin\java", there is no way to force that installer launcher to use that jre.
A bundled JVM is a self-extracting zip file for a platform it's defined. It should uncompress the contents to a current directory if you run that file (on a system it was created for). Once a bundled jvm is uncompressed, look for "jvm" file in the current directory and inspect the contents for JRE search instructions.
You may search support.installshield.com for the jvm file format and a custom jre bundling instructions.