[jbosstools-issues] [JBoss JIRA] (JBIDE-23142) [cdk][windows] If auto-discovered vagrant location in launch config is removed, shutdown fails

[ https://issues.jboss.org/browse/JBIDE-23142?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23142. --------------------------------- Assignee: Rob Stryker I tried this in devstudio 10.2.0.AM1 B6096. 1. I set up a cdk server normally. Make sure it works. 2. Quit devstudio 3. Make a new PATH entry in Windows for c:\HashiCorp-test\vagrant\bin in addition to c:\HashiCorp\vagrant\bin 4. Rename c:\HashiCorp to c:\HashiCorp-test 5. Reboot (for the new PATH entry to take effect) 6. Start devstudio 7. Open cdk server editor to see what happens This took a bit longer and the eclipse window even showed Not responding, so I was worried for a moment. But eventually it opened and when I checked launch config, it contained the new path. So I was happily surprised. I was then able to start cdk ok. It seems that some magic was happening when I was opening the server editor. So I wondered what would happen if I didn't open it and just tried to start cdk. So I carried on with the following: 8. Stop cdk, close cdk server editor and quit devstudio 9. Rename c:\HashiCorp-test back to c:\HashiCorp 10. Start devstudio 11. Launch cdk without opening the server editor first It still launched just fine. Then I carried on: 12. Stop cdk 13. Open cdk server editor 14. Open launch config And voila, the path to vagrant was already correct again. I still haven't verified the usecase when vagrant can't be located at all. So here's what I did: 15. Quit devstudio 16. Rename c:\HashiCorp to c:\HashiCorp-bla which is not on PATH 17. Start devstudio 18. Open cdk server editor + launch config I now get a warning that vagrant cannot be located. 19. Point the config to your new vagrant location 20. Start cdk It still works. So I'm quite happy that all the use cases seem to work. Closing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)