[jbosstools-issues] [JBoss JIRA] (JBDS-4065) DevStudio 1.1 Installer unfriendly when 1.0 present
Rob Stryker (JIRA)
issues at jboss.org
Fri Mar 10 11:06:00 EST 2017
[ https://issues.jboss.org/browse/JBDS-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Stryker updated JBDS-4065:
------------------------------
Fix Version/s: 10.4.0.AM2
(was: 10.4.0.AM1)
> DevStudio 1.1 Installer unfriendly when 1.0 present
> ---------------------------------------------------
>
> Key: JBDS-4065
> URL: https://issues.jboss.org/browse/JBDS-4065
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, platform-installer
> Affects Versions: 10.1.0.GA
> Environment: Windows 10, DevSuite Installer 1.0 had been run
> Reporter: Rick Wagner
> Assignee: Rob Stryker
> Fix For: 10.4.0.AM2
>
>
> When running the DevSuite 1.1 installer, DevStudio is not connected to the installed CDK.
> Observations:
> - All components removed before installation, does not help. (VirtualBox and Vagrant using Add/Remove programs, everything else directory-deleted, Environment variables cleaned).
> - DevStudio says it can't start the Container Development Environment server. ('Failed to find Vagrant!' reads the error). If I open Launch Configuration, it lists the Main as "C:\HashiCorp\Vagrant\bin\vagrant.exe", which is not in the installation directory.
> - It was noted that DevStudio marked itself 'completed' before Vagrant was installed. How does DevStudio know where Vagrant is?
> - It's noted that DevStudio 'remembers' user settings (i.e. CDK registration user/password) from previous attempts. Where is this information kept? I must've missed something in cleanup.
> - Tried full suite installation, then deleting DevStudio, then re-installing. (Hoping DevStudio would then find Vagrant in the right location, because it followed Vagrant's installation.) Result: No Container Development Environment server is present in 'server' view.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jbosstools-issues
mailing list