[
https://issues.jboss.org/browse/JBIDE-15614?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-15614:
---------------------------------------
[~rob.stryker], I just found out that I cannot connect to the server (EAP 6.2.0.ER4/ER5)
in MBean explorer - it shows the server as [disconnected] and cannot be connected. This
was with JBDS 7.1.0.Alpha2 B431. Is it related to what you described above?
Rename EAP 6.1 server type to 6.1+, ensure runtime detection is
accurate
------------------------------------------------------------------------
Key: JBIDE-15614
URL:
https://issues.jboss.org/browse/JBIDE-15614
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime-detection, server
Affects Versions: 4.1.0.Final
Environment: JBDS 7.0.0.GA
Reporter: Martin Malina
Assignee: Max Rydahl Andersen
Fix For: 4.1.1.Beta1
1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0.
2. When trying to add EAP 6.2 manually, there is no type EAP 6.2
Let me know if you want subtasks for these two.
--
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