[
https://issues.jboss.org/browse/JBIDE-17008?page=com.atlassian.jira.plugi...
]
Koen Aers commented on JBIDE-17008:
-----------------------------------
Since adding new runtimes is not supported anymore this is not going to be fixed. It is
now possible to run the pre-installed f1 and f2 runtimes side-by-side and to switch
between them.
Changing Forge runtimes is broken
---------------------------------
Key: JBIDE-17008
URL:
https://issues.jboss.org/browse/JBIDE-17008
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.2.0.Beta1
Reporter: Pavol Srna
Assignee: Koen Aers
Priority: Critical
Labels: regression
Fix For: 4.2.0.CR1
If there is currently running the embedded instance of forge runtime and an user attempts
to add a new runtime and attempts to use it right away -- then he is blocked and cannot
run any commands in the console.
He would need to change the runtime back to the embedded one (in preferences) - stop it
(in console view) and select the new one (in preferences) -- But even by doing that - the
start/stop buttons are not working properly.
Expected is that after changing the runtime it automatically restarts forge and uses the
new one. This is how it worked until Beta.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)