[jbosstools-issues] [JBoss JIRA] (JBIDE-21797) Fails to start the CDK server when it's was already started from CLI

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-21797:
-------------------------------------

The issue seems to be caused by an update to teh response to vagrant status --machine-readable. 

{code}
1457045944,cdk,state,running
1457045944,cdk,state-human-short,running
1457045944,cdk,state-human-long,The blahblahtruncated
1457045944,,ui,info,Current machine states:\n\ncdk blahblah truncated
{code}

The last line is only in vagrant 1.8.x, and you can notice the second field is empty.  This breaks our expectations as they were coded for vagrant 1.7.x. 

PR is available https://github.com/jbosstools/jbosstools-openshift/pull/1004

> Fails to start the CDK server when it's was already started from CLI
> --------------------------------------------------------------------
>
>                 Key: JBIDE-21797
>                 URL: https://issues.jboss.org/browse/JBIDE-21797
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 4.3.1.CR1
>            Reporter: Fred Bricon
>            Assignee: Rob Stryker
>             Fix For: 4.3.1.CR1
>
>
> - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI
> - once it's started, start the same CDK from the CDK server adapter
> => the server should detect the CDK already started and should simply be put in started mode, instead it fails to start with 
> !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650!



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