[
https://issues.jboss.org/browse/JBIDE-19288?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-19288:
-------------------------------------
Good catch. This is a bit of a regression from when we separated out the module state
verifier for filesystem and mangement profiles.
* f9f4055 - (mine/JBIDE-18861_maint, JBIDE-18861_maint) JBIDE-18861 - ensure module start
/ stop uses filesystem and marker operations rather than management when in a filesystem
profile (13 days ago, Rob Stryker)
So this affects current maintenance as well as of 2 weeks ago.
Module is not in Started state after deploy even though it is
deployed correctly.
---------------------------------------------------------------------------------
Key: JBIDE-19288
URL:
https://issues.jboss.org/browse/JBIDE-19288
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.0.Alpha1
Reporter: Radim Hopp
Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
When deploying project to running server (I've tried it with Wildfly 8 and EAP 6.3),
the project remains in state [Synchronized] instead of [Started, Synchronized] even though
the project is correctly deployed and running.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)