[
https://issues.jboss.org/browse/JBDS-3838?page=com.atlassian.jira.plugin....
]
Jan Richter commented on JBDS-3838:
-----------------------------------
The workaround works reliably if you follow the instructions the installer gives you if
VAGRANT_HOME is not in use.
But there is an issue (which I just discovered while re-checking the workflow) - the
contents of VAGRANT_HOME are not validated at all (JBDS-4058). The installer only checks
for the existence of the variable, so unless the user actually uses a valid path without
spaces, the installation will inevitably fail.
There is also an issue with CDK, which seems to prevent it from running when the user has
space in their name anyway (CDK-11).
As for the detailed steps:
- go to "Environment Variables" settings ( Control Panel -> System and
Security -> System -> Advanced System Settings -> Environment Variables | or
just use the start menu and search for "environment variables")
- under "User variables for $username" select "New..."
- Variable name: VAGRANT_HOME
- Variable value: a valid path without spaces
- keep clicking OK as long as there are windows that have the button
- start up the installer and now you should be able to continue
Cannot install CDK. Installer prompts to setup VAGRANT_HOME if there
is space in path and then it ignores it and fails
----------------------------------------------------------------------------------------------------------------------
Key: JBDS-3838
URL:
https://issues.jboss.org/browse/JBDS-3838
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: platform-installer
Affects Versions: 9.1.0.CR1
Reporter: Pavol Srna
Assignee: Denis Golovin
Priority: Blocker
Labels: havoc
Fix For: 10.0.0.Alpha1
Attachments: install.log, vagrant.log, vbox.log
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)