andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6,855 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
5b92adae1d
Go to file
Carsten Varming 5b92adae1d Use reflection to call cleaner on direct byte buffers in JDK9. 
Motivation:

Project Jigsaw in JDK9 has moved the direct byte buffer cleaner from
sun.misc.Cleaner to java.lang.ref.Cleaner$Cleanable. This cause the
current platform tests to throw a ClassNotFoundException, disabling the
use of direct byte buffer cleaners.

Modifications:

I use reflection to find the clean method in either sun.misc.Cleaner or
java.lang.ref.Cleaner$Cleanable.

Result:

Netty uses direct byte buffers on JDK9 as it already do on earlier JDKs.
2016-06-30 18:52:27 +02:00
all Update dependencies and plugins to latest possible versions. 2016-06-27 13:41:58 +02:00
buffer Test that CompositeByteBuf releases its components 2016-06-27 16:46:59 +02:00
codec Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:53:28 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-06-07 20:00:14 +02:00
codec-http Set some StackTraceElement on pre-instantiated static exceptions 2016-06-20 11:37:19 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-06-07 20:00:14 +02:00
common Use reflection to call cleaner on direct byte buffers in JDK9. 2016-06-30 18:52:27 +02:00
example Ensure examples are runnable in the ide 2016-06-20 07:11:43 +02:00
handler Fix NPE in OpenSslEngine 2016-06-30 11:13:22 +02:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2016-06-07 20:00:14 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-06-07 20:00:14 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2016-06-07 20:00:14 +02:00
testsuite-osgi Update dependencies and plugins to latest possible versions. 2016-06-27 13:41:58 +02:00
transport Allow to inject RejectedExecutionHandler for different EventLoops and EventExecutors 2016-06-24 17:57:34 +02:00
transport-native-epoll Allow to inject RejectedExecutionHandler for different EventLoops and EventExecutors 2016-06-24 17:57:34 +02:00
transport-rxtx Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:53:28 +02:00
transport-sctp Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:53:28 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-06-07 20:00:14 +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 Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
pom.xml Expose session ticket statistics. 2016-06-27 19:36:55 +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 logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +09:00

README.md

Netty Project

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

Links

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.