[jbosstools-issues] [JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE

Rob Stryker (JIRA) issues at jboss.org
Mon Nov 30 23:13:00 EST 2015


     [ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBDS-3549.
-------------------------------
    Resolution: Done


This has been committed to master and maintenance. 

The current implementation functions as a server adapter, and has all the pros and cons that that entails.  Server state may not always be 100% accurate upon initialization, or if user changes status via commandline.  However, attempts to start the CDK will succeed quickly if the CDK is already started. Attempts to stop the CDK will succeed quickly if the CDK is already stopped. 

All other functions behave as described above. 

> Developer - start and stop the CDK easily from within the IDE
> -------------------------------------------------------------
>
>                 Key: JBDS-3549
>                 URL: https://issues.jboss.org/browse/JBDS-3549
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Story
>          Components: server
>            Reporter: Max Rydahl Andersen
>            Assignee: Rob Stryker
>             Fix For: 9.1.0.Beta1, 10.0.0.Alpha1
>
>
> User Story:
> As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly.
> Acceptance Criteria:
> * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse
> * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse
> * If CDK is running, clicking stop should halt the CDK and docker
> * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing.



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


More information about the jbosstools-issues mailing list