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 install directory
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
‎Jan 21, 2013
05:29 AM
Overwrite bundled JVM install directory
Used version: IA 2011 SP3
Hi,
my installer installs the JVM into directory/_jvm
At JVM Settings -> Installer Settings I have set the option "Install Bundled".
I'd assume that the _jvm is always installed/overwritten, when the installer executes installation in the same directory.
But unfortunality the _jvm is not overwritten.
Any ideas to this?
--tf
Hi,
my installer installs the JVM into directory
At JVM Settings -> Installer Settings I have set the option "Install Bundled".
I'd assume that the _jvm is always installed/overwritten, when the installer executes installation in the same directory.
But unfortunality the _jvm is not overwritten.
Any ideas to this?
--tf
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 21, 2013
07:24 AM
Yes, the JVM is replaced by new one as soon as you click "Install" button (so between the pre-install & install phases).
Maybe some external software is locking it? on which OS is this happening?
Does activating installer debugging display some useful traces?
--Jerome
Maybe some external software is locking it? on which OS is this happening?
Does activating installer debugging display some useful traces?
--Jerome
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 21, 2013
09:00 AM
It happens on all OSs. The log tells me only (I've translated the localized output)
...
install directory: /foo/bar/_jvm
status: success
additional hint: directory already exists
install JRE: /foo/bar/_jvm
status: success
...
But the files in the JRE are not changed.
My "Default File Overwrite Behaviour" is set to "always overwrite".
Meanwhile I tried to configure, that the _jvm should be installed in $INSTALLER_TEMP_DIR$ and then during Install I add actions to move the /foo/bar/_jvm to /foo/bar/_jvm.bak and copy the $INSTALLER_TEMP_DIR$$/$_jvm to /foo/bar/_jvm.
Unfortunality, the Move and Copy does not preserve the file permissions, so all execution bits gets lost. So Move and Copy are pretty useless in Unix environments without some kind of "preserve file permissions".
PS: I just recognized, that the Platforms -> Enable setting unix file permission was disabled, maybe this is the reason for loosing file permissions on copy/move.
...
install directory: /foo/bar/_jvm
status: success
additional hint: directory already exists
install JRE: /foo/bar/_jvm
status: success
...
But the files in the JRE are not changed.
My "Default File Overwrite Behaviour" is set to "always overwrite".
Meanwhile I tried to configure, that the _jvm should be installed in $INSTALLER_TEMP_DIR$ and then during Install I add actions to move the /foo/bar/_jvm to /foo/bar/_jvm.bak and copy the $INSTALLER_TEMP_DIR$$/$_jvm to /foo/bar/_jvm.
Unfortunality, the Move and Copy does not preserve the file permissions, so all execution bits gets lost. So Move and Copy are pretty useless in Unix environments without some kind of "preserve file permissions".
PS: I just recognized, that the Platforms -> Enable setting unix file permission was disabled, maybe this is the reason for loosing file permissions on copy/move.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 21, 2013
10:31 AM
The generated installer script worked on the path with the old _jvm version, sorry for that.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 23, 2013
07:41 AM
Hi,
This is only installation traces, do you have more traces if you "export LAX_DEBUG=true" on the shell launching the Unix installer?
--Jerome
This is only installation traces, do you have more traces if you "export LAX_DEBUG=true" on the shell launching the Unix installer?
--Jerome