[
https://issues.jboss.org/browse/JBIDE-13033?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-13033:
---------------------------------------
I have one question here: Why not enable the editor when server is stopped (but there are
deployments)? You could argue that if the module is already deployed and you stop the
server and modify the deployment path it will break on the next start of the server. But
the same happens if you remove the deployment while stopped, modify the settings and then
add the deployment again - we don't prevent that.
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