[
https://issues.jboss.org/browse/JBIDE-23135?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-23135:
-------------------------------------
Jars that are different from our wf9 jars:
{code}
current jars eap7.1 jars
logging: 3.3.0.Final 3.3.0.Final =
sasl: 1.0.5.Final 1.0.5.Final =
threads: 2.2.1.Final 2.2.1.Final =
marshalling: 1.4.10.Final 1.4.11.Final *
remoting: 4.0.18.Final 4.0.21.Final *
dmr: 1.3.0.Final 1.4.0.Beta1 **
xnio: 3.3.4.Final 3.4.0.Final **
controller: 2.0.10.Final 3.0.0.Alpha8 ***
{code}
We can see the most likely area for breakage is the controller jars. For now everything
seems to work, but its worth noting that we may need yet another jar bundle if somehow
there are breakages in the major bump.
We curently have 3 jar sets labaled as as7, eap61plus, wildfly9. It would be a shame if we
needed a 4th set. For now it seems we don't need one, until we discover some
regressions.
EAP 7.1 Server adapter
----------------------
Key: JBIDE-23135
URL:
https://issues.jboss.org/browse/JBIDE-23135
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Reporter: Alexey Kazakov
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.4.2.AM3
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)