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

Rob Stryker (JIRA) issues at jboss.org
Mon Apr 14 09:00:34 EDT 2014


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

Rob Stryker commented on JBIDE-17102:
-------------------------------------

{code}
                public String getServerTypeId(String version) {
-                       if( version.equals(V8_0)) return IJBossToolingConstants.SERVER_WILDFLY_80;
-                       return null;
+                       // Just return adapter type wf8 until we discover incompatibility.
+                       return IJBossToolingConstants.SERVER_WILDFLY_80;
                }
{code}

That's the bug. Returning the latest version when we don't recognize seems the best idea. 

                
> 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


More information about the jbosstools-issues mailing list