Go to file
Xiaoyan Lin a96d52fe66 Fix javadoc links and tags
Motivation:

There are some wrong links and tags in javadoc.

Modifications:

Fix the wrong links and tags in javadoc.

Result:

These links will work correctly in javadoc.
2015-12-26 08:34:31 +01:00
all [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
buffer Fix javadoc links and tags 2015-12-26 08:34:31 +01:00
codec Fix javadoc links and tags 2015-12-26 08:34:31 +01:00
codec-dns [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-http Fix javadoc links and tags 2015-12-26 08:34:31 +01:00
codec-http2 Fix javadoc links and tags 2015-12-26 08:34:31 +01:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
common Fix javadoc links and tags 2015-12-26 08:34:31 +01:00
example [#4212] Backport WebSocket Extension handlers for client and server. 2015-12-18 09:48:10 +01:00
handler Fix javadoc links and tags 2015-12-26 08:34:31 +01:00
handler-proxy Extract SocketAdress logic from NameResolver 2015-12-14 14:03:50 +01:00
license [#4331] Helper methods to get charset from Content-Type header of HttpMessage 2015-11-19 15:59:34 -08:00
microbench Remove PriorityStreamByteDistributor from http2 microbench 2015-12-22 09:20:32 +01:00
resolver Have hosts file support for DnsNameResolver, close #4074 2015-12-17 15:15:42 +01:00
resolver-dns Fix javadoc links and tags 2015-12-26 08:34:31 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
transport Fix javadoc links and tags 2015-12-26 08:34:31 +01:00
transport-native-epoll Ensure closing a Socket / FileDescriptor multiple times will not throw exception 2015-12-23 23:04:30 +01:00
transport-rxtx Use OneTimeTask where possible to reduce object creation 2015-11-20 14:39:06 -08:00
transport-sctp Clear selectedKeys in OioSctpChannel.doReadMessages 2015-12-21 09:37:00 +01:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +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 [#4331] Helper methods to get charset from Content-Type header of HttpMessage 2015-11-19 15:59:34 -08:00
pom.xml ByteBufUtil.writeUtf8 Surrogate Support 2015-12-18 13:51:52 -08: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.