75e1b3e799
Motivation: If sun.nio.ch is not optional this will cause troubles in the OSGi world. The package is not exposed by default in OSGi, so actually the whole netty framework cannot be used directly. There are workarounds, but workarounds are ugly. Especially since the use of sun.nio.ch is optional. So the requirement on the package should be optional as well. Modifications: Make the import of sun.nio.ch optional. Result: If the package cannot be imported it will behave as if the package sun.nio.ch is not present (like with other JVMs). If the package is exposed in OSGi (e.g. bootclassloader delegation, extension fragment) it will be used. |
||
---|---|---|
all | ||
buffer | ||
codec | ||
codec-http | ||
codec-socks | ||
common | ||
example | ||
handler | ||
license | ||
microbench | ||
tarball | ||
testsuite | ||
transport | ||
transport-native-epoll | ||
transport-rxtx | ||
transport-sctp | ||
transport-udt | ||
.fbfilter.xml | ||
.fbprefs | ||
.gitignore | ||
.travis.yml | ||
CONTRIBUTING.md | ||
LICENSE.txt | ||
NOTICE.txt | ||
pom.xml | ||
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:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
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
The 'master' branch is where the development of the latest major version lives on. The development of all other major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.