[jbosstools-issues] [JBoss JIRA] (JBIDE-17102) WildFly 8.1.0.CR1 cannot be added using runtime detection

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-17102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-17102.
---------------------------------

    Resolution: Done


The new code will only break if we add a new server adapter. If a new wf-8.2 is released, and it is compatible with the existing wf server adapter type, then this will not break. We now no-longer return null, so we'll always return the existing wf runtime / server type id's. 

If it is incompatible, and we instead add a new wf8.2 server adapter type, then this line will need to be updated to return that. 

But assuming compatibility, the new code will work. It returns the proper wtp runtime and server id's, and that was the bug. 
                
> WildFly 8.1.0.CR1 cannot be added using runtime detection
> ---------------------------------------------------------
>
>                 Key: JBIDE-17102
>                 URL: https://issues.jboss.org/browse/JBIDE-17102
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Beta1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.2.0.Beta2
>
>
> When I try to add WildFly 8.1.0.CR1 using runtime detection, it is properly detected and the version number shown, but the runtime+server is not actually added if I press OK.
> You can get WildFly here: http://wildfly.org/downloads/
> Note that adding the server manually works (although you get a warning that it's a new version which may screw things up)

--
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