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

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-18861:
-------------------------------------

Ok... so i've verified it only happens when mixing filesystem vs management operations.   Because the deploy was done via filesystem, the 'stop' should also be done via filesystem, as should the start. So what this means is when the server is in non-management mode, we should not be doign a management-based stop / start.  We should be doing deployment marker  based start and stop of modules only (when server is in fs mode). 



> 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
>            Priority: Minor
>             Fix For: 4.2.2.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.8#6338)