[jbosstools-issues] [JBoss JIRA] (JBIDE-17102) WildFly 8.1.0.CR1 cannot be added using runtime detection
Martin Malina (JIRA)
issues at jboss.org
Tue Apr 15 04:18:33 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-17102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12961908#comment-12961908 ]
Martin Malina commented on JBIDE-17102:
---------------------------------------
The problem I can see here is that we don't offer any warning in the runtime detection - it either adds the runtime or it doesn't. It would be good if we could display a warning for any runtime found that is not tried&supported yet - the same way there is warning when you try to add WildFly 8.1 manually today - it lets you do it but it tells you that it might not work.
> 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