Go to file
2015-05-18 08:30:25 +02:00
all [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
buffer [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-dns [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-http Minor ClientCookieDecoder improvements 2015-05-12 11:25:28 +02:00
codec-http2 HTTP/2 GOAWAY Reference Count Issue 2015-05-15 10:48:41 -07:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
common ByteString test failure bug 2015-05-08 09:44:02 -07:00
example ALPN/NPN Examples Not using failure behavior compatible with all SslProviders 2015-05-08 09:39:09 -07:00
handler Fix typo in FingerprintTrustManagerFactory docs 2015-05-18 08:30:25 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
license Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 13:46:14 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
resolver [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
tarball [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
transport Scoring loopback addresses as 0 in DefaultChannelId 2015-05-08 13:14:36 -07:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Add JVM crash logs to .gitignore 2014-05-18 21:36:54 +09: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:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 13:46:14 +01:00
pom.xml [#3784] Support hostname verification when using OpenSSLEngine 2015-05-18 08:16:49 +02:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:24 -07:00
run-example.sh HTTP/2 examples run script support 2015-03-23 16:27:55 -07: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

The 'master' branch is where the development of the latest major version lives on. The development of all other 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.