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

Rob Stryker (JIRA) issues at jboss.org
Fri Feb 6 10:40:49 EST 2015


     [ https://issues.jboss.org/browse/JBIDE-18861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-18861.
---------------------------------
    Resolution: Done


I've merged the PR to maintenance since I feel it works as close to expected as possible. 

> 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.Beta1, 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)


More information about the jbosstools-issues mailing list