[jbosstools-issues] [JBoss JIRA] (JBIDE-17104) Add support for WildFly 8.1

Rob Stryker (JIRA) issues at jboss.org
Tue Apr 22 15:00:34 EDT 2014


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

Rob Stryker reassigned JBIDE-17104:
-----------------------------------

    Assignee: Martin Malina  (was: Rob Stryker)


The error message in the past used to read : 

This server type expects a version of {0} but the server directory is of version {1}. This combination may cause critical errors.

But I'm not able to replicate this, because wf 8.1 is still detected by the wildfly server bean loader, and the runtime and server type id's match what's expected, so no error is showing.   

I've made a commit to change everything to wf 8.x instead of 8.0, but I'd like confirmation on this last bit. 
                
> Add support for WildFly 8.1
> ---------------------------
>
>                 Key: JBIDE-17104
>                 URL: https://issues.jboss.org/browse/JBIDE-17104
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: server
>    Affects Versions: 4.2.0.Beta1
>            Reporter: Martin Malina
>            Assignee: Martin Malina
>             Fix For: 4.2.0.Beta2
>
>         Attachments: version-warning.png
>
>
> WildFly 8.1.0.CR1 is available here: http://wildfly.org/downloads/
> Currently runtime detection does not work properly - that is tracked in JBIDE-17102 .
> And when 8.1 is added manually, a warning is displayed that this is an unsupported version.
> We need to figure out if we need a new adapter for this version or support it using the current one and if so, rename it to 8.x perhaps.

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