Go to file
Nikolay Fedorovskikh 0a6df7b764 AbstractMethodError with barchart-udt
Motivation:

`SocketChannelUDT` from barchart-udt does not have the java 7 `public abstract SocketChannel bind(SocketAddress local)` method. Calling the abstract method `SocketChannel.bind(SocketAddress localAddress)` for `SocketChannelUDT` leads to an `AbstractMethodError` runtime error.

Modifications:

Make workaround with explicit call of `SocketChannelUDT.bind(SocketAddress local)` as it done in `NioUdtByteConnectorChannel`.

Result:

Fixes [#6934].
2017-07-05 07:35:46 +02:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:46 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-06-09 11:23:06 +02:00
bom [maven-release-plugin] prepare for next development iteration 2017-06-09 11:23:06 +02:00
buffer Move methods for decode hex dump into StringUtil 2017-06-23 19:01:30 +02:00
codec [maven-release-plugin] prepare for next development iteration 2017-06-09 11:23:06 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-06-09 11:23:06 +02:00
codec-http Performance improvement for HttpRequestEncoder. Insert char into the string optimized. 2017-06-27 11:11:55 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-06-09 11:23:06 +02:00
common Move methods for decode hex dump into StringUtil 2017-06-23 19:01:30 +02:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-06-09 11:23:06 +02:00
example [maven-release-plugin] prepare for next development iteration 2017-06-09 11:23:06 +02:00
handler Exhaust non-exhaustive switch cases 2017-06-27 07:56:54 +02:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:32:36 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2017-06-09 11:23:06 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2017-06-09 11:23:06 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2017-06-09 11:23:06 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-06-09 11:23:06 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-06-09 11:23:06 +02:00
transport Remove @deprecation keyword on AbstractUnsafe.ensureOpen(...) 2017-06-29 14:29:10 +02:00
transport-native-epoll Introduce EpollSocketChannelConfig.setTcpKeepCnt as replacement for setTcpKeepCntl. 2017-06-28 07:44:20 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-06-09 11:23:06 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-06-09 11:23:06 +02:00
transport-udt AbstractMethodError with barchart-udt 2017-07-05 07:35:46 +02:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:53:28 +02:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:32:36 +01:00
pom.xml Upgrade to netty-tcnative 2.0.5.Final 2017-06-25 19:03:50 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:09:30 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:50:53 +02:00

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

How to build

For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.

You require the following to build Netty:

Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+) is enough to run your Netty-based application.

Branches to look

Development of all versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.0 resides in the branch '3.9' and the branch '4.0' respectively.