Go to file
Trustin Lee 71737a2a65 Fix the build timeout when 'leak' profile is active
Motivation:

AbstractByteBufTest.testInternalBuffer() uses writeByte() operations to
populate the sample data.  Usually, this isn't a problem, but it starts
to take a lot of time when the resource leak detection level gets
higher.

In our CI machine, testInternalBuffer() takes more than 30 minutes,
causing the build timeout when the 'leak' profile is active (paranoid
level resource detection.)

Modification:

Populate the sample data using ThreadLocalRandom.nextBytes() instead of
using millions of writeByte() operations.

Result:

Test runs much faster when leak detection level is high.
2014-07-03 17:51:15 +09:00
all Add MQTT protocol codec 2014-06-21 16:51:37 +09:00
buffer Fix the build timeout when 'leak' profile is active 2014-07-03 17:51:15 +09:00
codec Fix most inspector warnings 2014-07-02 19:04:11 +09:00
codec-dns Fix most inspector warnings 2014-07-02 19:04:11 +09:00
codec-haproxy Fix test failures due to incorrect validation 2014-06-21 17:11:08 +09:00
codec-http Fix most inspector warnings 2014-07-02 19:04:11 +09:00
codec-http2 Removing unused Http2PrefaceHandler. 2014-07-02 07:10:55 -07:00
codec-memcache Fix most inspector warnings 2014-07-02 19:04:11 +09:00
codec-mqtt Mqtt -> MQTT 2014-06-21 17:14:20 +09:00
codec-socks Fix most inspector warnings 2014-07-02 19:04:11 +09:00
codec-stomp Fix most inspector warnings 2014-07-02 19:04:11 +09:00
common Fix the cruft produced from the refactoring 2014-07-02 20:30:45 +09:00
example Changed Http2ClientConnectionHandler to print out the aggregated buffers content 2014-07-03 07:06:19 +02:00
handler Fix most inspector warnings 2014-07-02 19:04:11 +09:00
license Implement a Bzip2Decoder 2014-06-24 14:49:49 +09:00
microbench Fix the inconsistencies between performance tests in ByteBufAllocatorBenchmark 2014-06-21 13:27:28 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2013-12-22 22:06:15 +09:00
testsuite Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport-native-epoll Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport-rxtx Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport-sctp Fix most inspector warnings 2014-07-02 19:04:11 +09:00
transport-udt Fix most inspector warnings 2014-07-02 19:04:11 +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:34:51 +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:17:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Implement a Bzip2Decoder 2014-06-24 14:49:49 +09:00
pom.xml Fix most inspector warnings 2014-07-02 19:04:11 +09:00
README.md Synchronized between 4.1 and master (part 3) 2014-04-25 16:17:16 +09:00
run-example.sh Overall refactoring of the STOMP codec 2014-06-04 17:09:11 +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 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.