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
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Overwrite bundled JVM when launching the installer
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
‎Aug 01, 2009
09:42 AM
Overwrite bundled JVM when launching the installer
Has anyone successfully done that? My installer bundles the JVM and we have an issues in the field that requires us to switch to a different JVM on the machine (higher version, but that is irrelevant here).
I've used install.exe -D$JAVA_HOME$=C:\jreblah and various permutation of that to no avail. I kept seeing the original JVM being extracted to temp, not the new one.
I am sure some of you have done this already. Maybe I did something wrong that someone can please point out?
Thanks!
I've used install.exe -D$JAVA_HOME$=C:\jreblah and various permutation of that to no avail. I kept seeing the original JVM being extracted to temp, not the new one.
I am sure some of you have done this already. Maybe I did something wrong that someone can please point out?
Thanks!
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 24, 2009
11:51 AM
The only workaround I could think of is to have a small action in the post-install that would patch the references to the jvm file to be used in all the .lax files from the old JVM to the new one. But why not bundle the newer one for all installations?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 06, 2009
10:37 PM
pv7721 wrote:
The only workaround I could think of is to have a small action in the post-install that would patch the references to the jvm file to be used in all the .lax files from the old JVM to the new one. But why not bundle the newer one for all installations?
Thanks for answering. It's easy if we can refresh the installer, but we do not want to ship a newer version of the product/installer every time we have this need :-).
Anyone from Acresso cares to comment?
Thanks
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 08, 2009
08:53 AM
There is a command-line argument called LAX_VM which is used to force the installer to use a particular JVM on target machine e.g. on command prompt :-
install.exe LAX_VM \path\to\java.exe
install.exe LAX_VM \path\to\java.exe
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)