[
https://issues.jboss.org/browse/JBIDE-22734?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-22734:
---------------------------------------
[~rob.stryker], maybe you missed that cdk was not started from the servers view at all. In
that case neither OpenShift connection, nor Docker connection will be created.
[~rick_wagner], I would like to note that even if you start cdk from command line (and
wait for it to start), you can then press the Run button in Servers view and the tools
will detect it running already, will just mark it as Started and create the connections
for you. Just in case you didn't know this.
I wonder how we can improve this. Perhaps at the end of the devsuite installer, just
before devstudio is launched, we could briefly note that to start using CDK, you can start
it from the Server view, once devstudio is launched?
Please clarify CDK usage
------------------------
Key: JBIDE-22734
URL:
https://issues.jboss.org/browse/JBIDE-22734
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: cdk, docker
Environment: CDK, as used in DevStudio and installed via Development Suite.
Reporter: Rick Wagner
* * This use case may be attributable to user error. Please weigh implementation cost
accordingly. * *
After using the Development Suite installer, the user arrives in a newly installed
DevStudio instance but without clear instructions on how to use the CDK. In my first
attempt, I relied upon previous CDK experience and went to a command-line to start the CDK
with 'vagrant up'. This resulted in a failure of later DevStudio components.
The proper trail is to go to the 'Servers' tab in DevStudio to bring up the
environment. (Then DevStudio components like the Docker explorer will properly
self-configure. This does *not* happen when the CDK is brought up manually as I had
done.)
Please consider, look for ways to prevent other users from taking a similar path.
Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)