[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-5865) Bahaviour of "Make Deployable" and "Make Undeployable" is not consistent
[
https://jira.jboss.org/jira/browse/JBIDE-5865?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-5865:
---------------------------------------
Component/s: JBossAS
Fix Version/s: 3.2.next
Priority: Minor (was: Major)
Im hearing you but not sure i'm fully agreeing.
At "make deployable" we got *1* resource that can be pushed to *multiple*
servers, meaning there is clear understanding where we are coming from and going too.
At *make undeployable* we got 1 resource possibly published to many servers .... and
marking the resource nondeployable does not necessarily mean you want it removed from a
server...
Bahaviour of "Make Deployable" and "Make
Undeployable" is not consistent
------------------------------------------------------------------------
Key: JBIDE-5865
URL: https://jira.jboss.org/jira/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.next
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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira