–1 (non-binding) I went to test 2.18.1 (then 2.18.2-SNAPSHOT) on my project, and discovered a problem with the camel-ahc component. It’s complicated…but here’s what’s happening.
AsyncHttpClient 2.0.15 (used by Camel 2.18.2-SNAPSHOT) depends on netty 4.0.41.Final. AsyncHttpClient 2.0.15 was using the io.netty.util.internal package (which presumably is so named because netty intends it for internal use only). In the latest netty (4.1.7.Final, backported to 4.0.43.Final), netty refactored the code that AsyncHttpClient was using. The problem here arises when there are multiple modules within the project with dependencies on netty, and maven dependency resolution chooses the latest version referenced by any pom. In the case of my project, the dependency tree shows version 4.1.7.Final is used, which breaks AsyncHttpClient 2.0.15. AsyncHttpClient has fixed this problem, so I think (hope) updating ahc-version to 2.0.27 in parent/pom.xml will resolve this problem. Thanks, Mark On January 22, 2017 at 3:26:54 PM, Gregor Zurowski (gre...@list.zurowski.org<mailto:gre...@list.zurowski.org>) wrote: Hi Everyone: This is a vote to release Apache Camel 2.18.2, a new patch release that includes 68+ fixes and improvements. Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338705&projectId=12311211 Staging repository: https://repository.apache.org/content/repositories/orgapachecamel-1066/ Tarballs: https://repository.apache.org/content/repositories/orgapachecamel-1066/org/apache/camel/apache-camel/2.18.2/ Tag: https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=20ea3627daba0bc0e0759bcecb6cf0d7ee0c542c Please test this release candidate and cast your vote. [ ] +1 Release the binary as Apache Camel 2.18.2 [ ] -1 Veto the release (provide specific comments) The vote is open for at least 72 hours. Thanks, Gregor
