]
Denis Golovin commented on JBDS-3761:
-------------------------------------
VirtualBox msi installer adds target location to System environment, which is not
available in you current environment until you at leas log off and log in. Sometimes even
reboot required in rare scenarios.
You also can get in another 'bad state' when you installed virtualbox restarted,
then uninstalled it and start Developer Platform installer. In this scenario uninstalled
VirtualBox is going to be detected because system environment variables are still the
same. In this case log-in/log-off workaround would not help. You will see there is no
virtualbox signs in system environment but if you say echo %PATH% there would be an entry
for uninstalled virtualbox. That can be fixed only with restart.
when replacing an existing VBox install, should use the same install
folder; could also ask user where they want VirtualBox installed
-------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-3761
URL:
https://issues.jboss.org/browse/JBDS-3761
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Nick Boldt
Fix For: 9.1.0.GA
Attachments: JBDS3761-VBox508installed-but-honeybadger-installer-doesnt-care.png,
vbox-install-omits-guestadditions.png
I had Virtual Box 5.0.16 installed.
The dev platform installer (build 33) decided 5.0.16 was bad, uninstalled it, and instead
installed 5.0.8 into C:\DeveloperPlatform\virtualbox (where I had had it installed to the
default folder, c:\Program Files\Oracle\VirtualBox.
As a result, my existing VB install cannot find the Guest Additions iso image.
!vbox-install-omits-guestadditions.png!
I suggest that since the installation of Virtual Box isn't something that is
necessarily tied into the DevPlatform, it should be installed into its default folder,
c:\Program Files\Oracle\VirtualBox, rather than C:\DeveloperPlatform\virtualbox.
Or if not, the installer could ask the user if they want to use the default folder (for
reuse) or install under the DeveloperPlatform folder (for a more self-contained
installation footprint).