[jbosstools-issues] [JBoss JIRA] (JBIDE-17616) bring back externally managed to server and new wizard UI
[
https://issues.jboss.org/browse/JBIDE-17616?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-17616:
---------------------------------------
[~maxandersen], yeah, I get your point. Before the change, we argued that if you want to
enable a start/stop script and go to Launch config, you learn that you can't set it up
- you have to go back, click the checkbox and then go back to Launch config.
But now similarly, when a user wants to disable start/stop scripts, he has to go to Launch
config first. I agree that it's not perfect either. But in my opinion better than
before.
How would you expect to have both? Have the same checkbox in both places? Would that be
confusing?
bring back externally managed to server and new wizard UI
---------------------------------------------------------
Key: JBIDE-17616
URL: https://issues.jboss.org/browse/JBIDE-17616
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: server
Reporter: Max Rydahl Andersen
Priority: Critical
in JBIDE-17076 externally managed was *moved* into launch UI even though that externally
managed defaults to false and when users enable it launch configurations becomes
irrelevant.
Why can't we have it both so we do not have to get users to work with launch
configuraiton UI for the simple case of not wanting to start a server but just connect to
what is there ?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)