[jbosstools-issues] [JBoss JIRA] (JBIDE-22608) Support scenario when cdk is stopped from cli and then in devstudio

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-22608:
---------------------------------------

[~rob.stryker], ok, it works now on first attempt in devstudio 10 and cdk 2.1. Strange. Of course I wouldn't have reported this if I hadn't seen it :) 
Second time I tried with the shared folder Vagrantfile:
1. Start cdk in cli
2. Start adapter - is marked as started
3. Stop cdk in cli
4. Now I wanted to stop the adapter - but the stop button is displayed.
Any idea why that's happening, [~rob.stryker]? The only button that is enabled now is Restart. (And the status is Started.)

> Support scenario when cdk is stopped from cli and then in devstudio
> -------------------------------------------------------------------
>
>                 Key: JBIDE-22608
>                 URL: https://issues.jboss.org/browse/JBIDE-22608
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: cdk
>    Affects Versions: 4.4.0.Final
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>
> Assume your cdk is started and it's shown as started in devstudio, now what if you stop cdk from cli for whatever reason? Currently the tooling can't handle such situation.
> If you then try to stop cdk in devstudio, you get an error pop-up:
> Server Container Development Environment failed to stop.
> And the console will just say:
> ==> default: VM not created. Moving on...
> But most importantly, the server adapter will stay in the Started state.
> We should probably support this scenario - it's quite likely that it will happen to users. 
> Right now there are several ways out of this situation:
> a) Start cdk from cli again and everything will probably work as expected
> b) Restart your IDE
> So I suggest we improve the tooling in such a way that when you stop cdk, it will be able to detect that it's actually not running and just change the state to Stopped. It may be still ok to pop up the error saying it failed to stop. But at least you can now start it again from the IDE.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)