Go to file
Scott Mitchell 328a1ec01b cleanup from 819b26b
Motivation:
I cherry-picked 819b26b too soon. There were entries added to a deprecated class which should only go into the non-deprecated version of the class.

Modifications:
- Remove the static final variables that were added as duplicates to the deprecated class

Result:
Deprecated code does not grown in volume without need.
2016-06-14 09:28:35 -07:00
all [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
buffer [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
codec Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
codec-http cleanup from 819b26b 2016-06-14 09:28:35 -07:00
codec-http2 Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
codec-redis [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
common Logs in invokeExceptionCaught have been made consistent and full 2016-06-11 20:11:11 +02:00
example [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
handler Fix for a newly intrduced bug in #5377 2016-06-13 20:28:17 +02:00
handler-proxy Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02:00
license added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
resolver [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
resolver-dns Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +02:00
transport AbstractBootstrap can crash instead of failing promise, close #5387 2016-06-13 18:59:09 +02:00
transport-native-epoll Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02:00
transport-rxtx Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02:00
transport-sctp Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-06-07 18:52:34 +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:19:45 +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:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
pom.xml Make JCtools available (provided scope) for tests and optional OSGI, issue #5383 2016-06-11 07:15:48 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +01:00
run-example.sh Add an example client for codec-redis 2016-04-23 11:18:12 -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

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.