[jbosstools-issues] [JBoss JIRA] (JBDS-4065) DevStudio 1.1 Installer unfriendly when 1.0 present

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13300140#comment-13300140 ] 

Martin Malina commented on JBDS-4065:
-------------------------------------

Correct me if I'm wrong, but it seems that in your existing workspace, cdk was already set up before your cleanup and new devsuite install.
Both path to Vagrantfile and path to vagrant are set up when the server adapter is created in devstudio and it is then stored in the workspace. (Credentials are stored in Eclipse Keychain - there should be one per user account.)
So if this was the case, it is kind of expected that when you set up a server adapter and then change your vagrant installation to a different directory, this server adapter will no longer work. It's true that we could possibly improve this so that vagrant is searched for each time it's needed - not just once during server adapter creation. But it could be a potentially expensive operation, so I'm not sure it's something we'd want.

> 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
>
> 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
(v6.4.11#64026)