Go to file
Scott Mitchell 5ed89648c3 MqttEncoder build failure
Motivation:
The MqttEncoder was failing to build because it was using a method that doesn't exist.

Modifications:
Change sessionPresent() to isSessionPresent().

Result:
MqttEnccoder is now able to build.
2015-07-30 10:20:01 -07:00
all [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
buffer [#3896] Unpooled.copiedBuffer(ByteBuffer) and copiedBuffer(ByteBuffer...) is not thread-safe. 2015-07-07 08:38:37 +02:00
codec XmlFrameDecoder is corrupt 2015-07-29 18:49:26 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04: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 HttpObjectDecoder performance improvements 2015-07-29 23:26:26 -07:00
codec-http2 Use standard syntax for logging HTTP/2 stream ID. 2015-07-28 09:54:14 -07:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04: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 [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 (fix) typo 2015-07-30 12:49:25 +02:00
example HTTP/2 Example Needs FullHttpRequest 2015-07-07 13:50:23 -07:00
handler [#3968] Disallow pass-through of non ByteBufs in SslHandler 2015-07-22 13:31:33 +02: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 HttpObjectDecoder performance improvements 2015-07-29 23:26:26 -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 [#3987] Remove RC4 from default ciphers. 2015-07-22 13:29:43 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-05-07 14:21:08 -04:00
transport Correctly count acquired channels when timeout occurs in FixedChannelPool 2015-07-30 07:55:46 +02:00
transport-native-epoll Make IntObjectHashMap extend Map 2015-07-22 15:52:27 -07: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 Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:38:11 +02:00
pom.xml Correctly handle errors when using OpenSSL 2015-06-21 21:06:42 +02: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.