[jbosstools-issues] [JBoss JIRA] (JBIDE-18861) module start action does not delete *.undeployed file

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032736#comment-13032736 ] 

Martin Malina commented on JBIDE-18861:
---------------------------------------

[~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.

> module start action does not delete *.undeployed file
> -----------------------------------------------------
>
>                 Key: JBIDE-18861
>                 URL: https://issues.jboss.org/browse/JBIDE-18861
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>         Environment: Windows7 64bit, JDK 8u25
>            Reporter: Darryl Miles
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: 4.2.3.Final, 4.3.0.Alpha1
>
>
> If you start Wildfly with all modules enabled and started.
> Now use STOP action on an EAR module.
> Now stop Wildfly.
> Now start Wildfly (debug or run).
> It will start up without the EAR module running, this is correct behavior at this point.
> Now use START on EAR module.  It fails to start at all.
> This is because the file *.undeployed still exists.  If you manually remove the file (using system file manager) the module will start up.
> If you perform a "full publish" on the module that appears to cause it to start up as well.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)