[jbosstools-issues] [JBoss JIRA] (JBIDE-17008) Changing Forge runtimes is broken

Koen Aers (JIRA) issues at jboss.org
Thu May 22 10:40:57 EDT 2014


    [ https://issues.jboss.org/browse/JBIDE-17008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969787#comment-12969787 ] 

Koen Aers commented on JBIDE-17008:
-----------------------------------

Postponing to 4.2.0.Beta3

> 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.Beta3
>
>
> 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.2.3#6260)


More information about the jbosstools-issues mailing list