[
https://issues.jboss.org/browse/JBIDE-13136?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-13136:
---------------------------------------
yes, this is basically fixed. but in one scenario it doesn't work as expected.
Rob, you said the changes should be enabled only if the server has 0 modules and is fully
synchronized. See these steps:
1. Server is started and module is deployed - editing disabled - fine
2. Stop server - editing disabled - fine
3. Remove module - editing enabled! - FAIL - it should still be disabled unless you click
Publish on the server
Created JBIDE-13195 for that. But I think we can live without it in JBT 4.0.0 - it should
force another respin.
Deployment tab of server editor is always disabled
--------------------------------------------------
Key: JBIDE-13136
URL:
https://issues.jboss.org/browse/JBIDE-13136
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.CR1
Environment: JBDS 6.0.0.CR1 B111
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Blocker
Labels: respin-b
Fix For: 4.0.0.CR1
The Deployment tab of server editor is disabled even if it shouldn't be.
Just add a AS 7.1.1 server and you'll see it (no projects needed).
This may be a regression from JBIDE-13033
I saw this in two different instances of JBDS so hopefully you will be able to replicate
this.
--
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