[
https://issues.jboss.org/browse/JBIDE-13033?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-13033:
---------------------------------------
You're right, when you remove a deployed module on a stopped server, the Publish
button removes it - I didn't know that. But that shows something - when you remove a
module shouldn't it be removed right away?
Consider this:
When you copy a deployment on a stopped server, it is copied there right away.
When you remove a deployment from a stopped server, it is not removed right away - you
need to click Publish. Can we change that? So that the "unpublish" of the
removed module is done immediately? If you agree I'll create a JIRA for that.
So the above is my only remaining concern here. Otherwise you're right and I was wrong
:)
When server editor is closed and opened Deployment tab is enabled
even if it should not
---------------------------------------------------------------------------------------
Key: JBIDE-13033
URL:
https://issues.jboss.org/browse/JBIDE-13033
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.Beta2
Environment: JBT 4.0.0.Beta2 B43
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.0.0.CR1
Not sure how you control the disabling of the Deployment tab, but it doesn't always
work correctly.
When it's disabled and you reopen (close&open) the server editor it is enabled
again.
Also the comment at the top of the Deployment tab says:
"Settings on this page may only be modified if the server has 0 modules and is fully
synchronized."
- this is not totally accurate - should have something like: "or the server is
stopped"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira