Go to file
fbregier 7327d681bb Fix for issue #2765 relative to unstable trafficshaping test procedure
Motivation:

The test procedure is unstable due to not enough precise timestamping
during the check.

Modifications:

Reducing the test cases and cibling "stable" test ("timestamp-able")
bring more stability to the tests.

Result:

Tests for TrafficShapingHandler seem more stable (whatever using JVM 6,
7 or 8).
2014-08-15 10:09:45 -07:00
all [maven-release-plugin] prepare for next development iteration 2014-08-14 09:41:33 +09:00
buffer [maven-release-plugin] prepare for next development iteration 2014-08-14 09:41:33 +09:00
codec Fix and clearify javadocs 2014-08-14 06:43:22 +02:00
codec-http [#2768] Correctly duplicate buffer for CloseWebSocketFrames 2014-08-14 09:50:40 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-08-14 09:41:33 +09:00
common Reduce the fallback SOMAXCONN value 2014-08-14 15:42:22 -07:00
example [maven-release-plugin] prepare for next development iteration 2014-08-14 09:41:33 +09:00
handler [maven-release-plugin] prepare for next development iteration 2014-08-14 09:41:33 +09:00
license Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2014-08-14 09:41:33 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2014-08-14 09:41:33 +09:00
testsuite Fix for issue #2765 relative to unstable trafficshaping test procedure 2014-08-15 10:09:45 -07:00
transport Fix a bug where ChannelOutboundBuffer.removeBytes() throws ClassCastException 2014-08-15 09:56:47 -07:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2014-08-14 09:41:33 +09:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-08-14 09:41:33 +09:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-08-14 09:41:33 +09:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-08-14 09:41:33 +09: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:37:12 +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:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2014-08-14 09:41:33 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07:00
run-example.sh Use a forked exec-maven-plugin instead of maven-antrun-plugin 2014-05-23 20:06:12 +09: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 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.