]
Jeff Mesnil resolved AS7-5402.
------------------------------
Resolution: Rejected
we will keep netty 3.2.6.Final for now
upgrade netty to 3.4.5.Final
----------------------------
Key: AS7-5402
URL:
https://issues.jboss.org/browse/AS7-5402
Project: Application Server 7
Issue Type: Component Upgrade
Components: JMS, Web Services
Affects Versions: 7.1.2.Final (EAP)
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 7.2.0.Alpha1
When I upgraded HornetQ to 2.2.19.Final, I did not update Netty to the same version that
HornetQ requires (from 3.2.6.Final to 3.4.5.Final).
What's more, with this version, Netty changeed its groupId in Maven from
org.jboss.netty to io.netty.
HornetQ is not the only component that depends on Netty (jbossws uses it too) and I am
not sure jbossws is ready to update its version of Netty.
Since the groupId of Netty changed, I propose to add a new module io.netty and upgrade
its Netty versiontto 3.4.5.Final. HornetQ modules will then depend on that module.
I will *not* change the current org.jboss.netty module (that is used by jbossws)
--
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: