[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5865) Bahaviour of "Make Deployable" and "Make Undeployable" is not consistent

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-5865:
------------------------------------

Expected behaviour is 2) or both deploy/undeploy immediately. 

It seems it's even coded to do that, however, as per another WTP bug, and partly a bug in our code, we are not prepared to handle the removal of DeletedModule objects and our publisher fails to undeploy it properly. It removes it from the server as far as hte tooling is concerned but hte file is not actually removed from the filesyste,. 

> Bahaviour of "Make Deployable" and "Make Undeployable" is not consistent
> ------------------------------------------------------------------------
>
>                 Key: JBIDE-5865
>                 URL: https://jira.jboss.org/browse/JBIDE-5865
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.1.0.CR2
>            Reporter: Dominik Pospisil
>            Priority: Minor
>             Fix For: 3.2.x
>
>
> When "Make Deployable" is applied to a resource, and a server is running, it gets immediatelly deployed.
> When "Make Undeployable" is applied to a resource on running server, it is correctly removed from a list of resources available for deployment, but it is not undeployed.
> Make Deployable/Undeployable should:
> 1) not deploy/undeploy resource immediately (preferably)
> 2) or both deploy/undeploy immediately.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira