[
https://issues.jboss.org/browse/JBIDE-15619?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-15619:
-------------------------------------
For master and maintenance, as far as I can tell, eap6.2 er4 works without error now.
For released tools, EAP6.2 ER4 will work fine if created from the new server wizard, using
the eap6.1 server type. However, it will NOT work properly when using runtime detection,
as the runtime detection will get the version wrong (6.0) and then try to create an eap6.0
server type to represent it. It will then obviously fail because of the filesystem layout
changes between eap6.0 and eap6.1.
There's nothing we can do here to fix it except advise users to upgrade to
maintenance, or, to create their server via the new server wizard instead of the runtime
detection.
Verify EAP 6.2 ER4 works without error
---------------------------------------
Key: JBIDE-15619
URL:
https://issues.jboss.org/browse/JBIDE-15619
Project: Tools (JBoss Tools)
Issue Type: Task
Components: server
Affects Versions: 4.2.0.Alpha1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.2.0.Alpha1
Do a smoke-test on all aspects of EAP6.2 ER4, including startup, shutdown, management,
deployment, pollers, etc.
--
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