On Tuesday, March 22, 2016 11:10:48 PM Chris Nauroth wrote: > I understand now. I was looking strictly at the dependencies defined in > ivy.xml, where the Netty dependency's "org" (or "groupId" in Maven-speak) > has already made the switch from "org.jboss.netty" to "io.netty". The > classes are still under the "org.jboss.netty" package at the Java level > though. Your proposal is to move to the 4.x line for Netty, where the > classes are under the "io.netty" Java package.
If you try to compile after changing from org.jboss to io.netty, it should fail due to Netty API changes. First thing I tried and really hoped all it was just a simple package change. Of course it ended up not being the case :( > In any case, I see you filed ZOOKEEPER-2399. Using a JIRA to track the > proposal is the right next step, so thank you for doing that. Your welcome, just following instructions per the provided link. Seems I guessed the first step right by mentioning it here on list before creating bug. But I did file the issue, and attached files as we all know from Jira posting to list. This likely concludes my involvement though will remain on list for a bit. Of course will remain on bug and respond to any comments/questions. But really at the extent of what I can contribute for now. Very appreciative in advance for whom ever finishes the work I started. Hopefully what I did is usable, or at least will give some hints as to how to refactor the code for Netty 4.x API. I will see about adding the docs I used as reference to the bug. If anything else let me know. Otherwise good luck, and thanks! -- William L. Thomson Jr. Obsidian-Studios, Inc. http://www.obsidian-studios.com
