[
https://issues.jboss.org/browse/JBIDE-23660?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-23660:
-------------------------------------
According to the code, shutdown uses "vagrant halt", not vagrant destroy.
In fact, there's only 2 mentions of the term "destroy" anywhere in the CDK
plugins, and that's just to destroy the "vagrant halt" process if the
process takes too long to complete.
As far as I can tell, we never run vagrant destroy.
CDK Server adapter should have an option to configure stop command
------------------------------------------------------------------
Key: JBIDE-23660
URL:
https://issues.jboss.org/browse/JBIDE-23660
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: cdk
Affects Versions: 4.4.2.Final
Reporter: Ricardo Martinelli Oliveira
Assignee: Rob Stryker
CDK Server adapter lets configure the vagrant startup options. There should have an
option to do the same in the stop.
Why?
It seems that CDK Server adapter uses _vagrant destroy_ to stop CDK, but using that
option has its drawbacks, like for example:
* If I'm stopping it to save resources, then I'm loosing all my job in it.
* All images already pulled will be lost, so I cannot work offline
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)