Go to file
Norman Maurer d4a1665941 Fix SSLEngineTest handshake method.
Motivation:

We used && in the handshake method of SSLEngineTest but it must be ||.

Modifications:

Changed && to ||

Result:

Correctly check condition
2016-01-27 08:58:45 +01:00
all [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
buffer [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
codec [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
codec-dns [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
codec-http Set default CONTENT_TYPE when it is absent in multipart request body 2016-01-26 10:47:11 +01:00
codec-http2 [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
codec-memcache More efficiently allocate header buffer. 2016-01-26 10:14:51 +01:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
codec-xml [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
common [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
example [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
handler Fix SSLEngineTest handshake method. 2016-01-27 08:58:45 +01:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01: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-01-21 15:35:55 +01:00
resolver [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
testsuite [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
transport Fix ChannelOutboundHandlerAdapter javadoc 2016-01-26 10:13:16 +01:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01: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 added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
pom.xml [maven-release-plugin] prepare for next development iteration 2016-01-21 15:35:55 +01:00
README.md Fix the 'branches to look' section 2015-10-27 13:59:11 +01: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.