Go to file
Scott Mitchell beab89bec5 Remove Erroneous imports
Motivation:
As part of merging / cherry-picking there were some Erroneous imports added to AbstractMemcacheObjectAggregator.

Modifications:
- Remove Imports from AbstractMemcacheObjectAggregator.

Result:
Code now builds.
2015-08-17 10:12:43 -07:00
all [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
buffer MemoryRegionCache$Entry objects are not recycled 2015-08-10 21:29:25 +02:00
codec HttpObjectAggregator doesn't check content-length header 2015-08-17 09:26:50 -07:00
codec-dns maxBytesPerRead channel configuration 2015-08-05 23:59:54 -07:00
codec-haproxy Add ProtocolDetectionResult and use it in HAProxyMessageDecoder for allow detect HAProxy protocol. 2015-06-23 08:59:07 +02:00
codec-http HttpObjectAggregator doesn't check content-length header 2015-08-17 09:26:50 -07:00
codec-http2 Headers Performance Boost and Interface Simplification 2015-08-17 08:50:11 -07:00
codec-memcache Remove Erroneous imports 2015-08-17 10:12:43 -07:00
codec-mqtt MqttEncoder build failure 2015-07-30 10:20:01 -07:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
codec-stomp HttpObjectAggregator doesn't check content-length header 2015-08-17 09:26:50 -07:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
common Headers Performance Boost and Interface Simplification 2015-08-17 08:50:11 -07:00
example Headers Performance Boost and Interface Simplification 2015-08-17 08:50:11 -07:00
handler Eclipse SPDY docs moved 2015-08-13 09:45:06 -07:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:38:11 +02:00
microbench Headers Performance Boost and Interface Simplification 2015-08-17 08:50:11 -07:00
resolver [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
resolver-dns DnsResolver.resolve(...) fails when ipaddress is used. 2015-07-18 17:14:05 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
testsuite Allow to create SslContext from existing PrivateKey / X509Certificate 2015-08-12 15:05:58 +02:00
testsuite-osgi Add a property to disable osgi testsuite run 2015-08-13 09:53:26 +09:00
transport Fixing compile error, introduce by 5d011b8895 2015-08-12 14:25:45 +02:00
transport-native-epoll Add support for abstract domain sockets 2015-08-16 20:03:23 +02:00
transport-rxtx maxBytesPerRead channel configuration 2015-08-05 23:59:54 -07:00
transport-sctp maxBytesPerRead channel configuration 2015-08-05 23:59:54 -07:00
transport-udt maxBytesPerRead channel configuration 2015-08-05 23:59:54 -07: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 Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:38:11 +02:00
pom.xml Upgrade jacoco-maven-plugin to the latest version 2015-08-16 19:24:50 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:24 -07:00
run-example.sh Add HTTP/2 Netty tiles example 2015-05-18 14:16:54 -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.