Motivation: If unsafe is unavailable, we can not use the cleaner anyway. If we try to set it up, we get an annoying log message about unsafe being unavailable (when debug logging is enabled). We know this will fail, so we should not even bother and avoid the log message. Modifications: This commit adds a guard against setting up the cleaner if it is not going to be available because unsafe is unavailable. Result: We do not try to set up the cleaner if unsafe is unavailable, and we do not get an annoying log message.
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:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
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.
Description
Languages
Java
99.8%
Shell
0.1%