[
https://issues.jboss.org/browse/JBIDE-22646?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-22646:
-------------------------------------
Since there is no process that we launched, it's expected the process disappears in
this case. Generally you only want a process in the view if a process is running that can
be identified and terminated. Since we cannot identify the process actually running the
VM, we only have the vagrant up process associated with the launch, and once that
completes, the process (and thus launch) are completed.
You can contrast this with a remote wildfly startup for example, where we keep the process
in the view because we know there is a remote process and we know it's PID. So we
simulate the process in that situation.
I'd suggest this is working as expected.
Starting cdk creates two processes in debug view
------------------------------------------------
Key: JBIDE-22646
URL:
https://issues.jboss.org/browse/JBIDE-22646
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdk, server
Affects Versions: 4.4.1.AM1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.4.1.AM1
Starting cdk creates two processes in debug view.
One does not disappear when the startup process is complete.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)