[ https://issues.jboss.org/browse/JBIDE-18861?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-18861 at 1/15/15 7:49 AM: ---------------------------------------------------------------- [~rob.stryker], when I followed the steps, I noticed that when I stopped the module, it was undeployed and then the server said: {code} 13:46:20,300 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found earproj.ear in deployment directory. To trigger deployment create a file called earproj.ear.dodeploy {code} I know it's kind of expected - we would need to remove the contents of the ear from the folder to avoid this. Do you think it's ok? But then, when I carried on, after I stopped and started Wildfly, the module was shown as [Synchronized] in the server view and it was not running. Shouldn't it say [Stopped, Synchronized]? I was then able to start it and it worked, so in this regard it's ok. (I tried this on master from a few days ago.) was (Author: mmalina): [~rob.stryker], when I followed the steps, I noticed that when I stopped the module, it was undeployed and then the server said: {code} 13:46:20,300 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found earproj.ear in deployment directory. To trigger deployment create a file called earproj.ear.dodeploy {code} I know it's kind of expected - we would need to remove the contents of the ear from the folder to avoid this. Do you think it's ok? But then, when I carried on, after I stopped and started Wildfly, the module was shown as [Synchronized] in the server view and it was not running. Shouldn't it say [Stopped, Synchronized]? I was then able to start it and it worked, so in this regard it's ok. -- This message was sent by Atlassian JIRA (v6.3.11#6341)