[
https://issues.apache.org/jira/browse/CAMEL-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-6555:
-------------------------------
Fix Version/s: (was: Future)
2.12.0
The new camel-netty-http is intended to be upgraded for Netty 4.x so when we
release Camel 2.12 this component requires Netty 4.x.
The existing camel-netty can be renamed to camel-netty3 having it as netty3
component for backwards compatible Camel users. So their migration is easy,
just use netty3 as component name.
In the mean time we have a camel-netty4 module for the work in progress upgrade
to Netty 4.x. When this is complete we can do the component renames.
So after the upgrade we have
- camel-netty3 = the old 3.x netty based
- camel-netty = the new 4.x netty based
> camel-netty - Upgrade to Netty 4
> --------------------------------
>
> Key: CAMEL-6555
> URL: https://issues.apache.org/jira/browse/CAMEL-6555
> Project: Camel
> Issue Type: Task
> Components: camel-netty
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.12.0
>
>
> Netty 4.0 has been released. We should upgrade, though it has new package
> names. So end users with custom codec need to migrate as well.
> So we could indicate that after Camel 2.12 we upgrade to give ppl amble time
> to adjust.
--
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
