Go to file
Norman Maurer 06d76eeea4 Update tcnative version
Motivation:

Previous tcnative version had a bug with the uberjar on windows.

Modifications:

Update version.

Result:

Depend on latest tcnative version.
2016-05-22 17:47:35 +02:00
all [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
buffer Add CompositeByteBuf.addComponent(boolean ...) method to simplify usage 2016-05-21 19:52:16 +02:00
codec Add CompositeByteBuf.addComponent(boolean ...) method to simplify usage 2016-05-21 19:52:16 +02:00
codec-dns Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
codec-http Add CompositeByteBuf.addComponent(boolean ...) method to simplify usage 2016-05-21 19:52:16 +02:00
codec-http2 Add CompositeByteBuf.addComponent(boolean ...) method to simplify usage 2016-05-21 19:52:16 +02:00
codec-memcache Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-mqtt Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-redis Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-smtp Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-socks Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-stomp Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
codec-xml Update dependencies 2016-04-14 11:05:53 +02:00
common Mark Recycler.recycle(...) deprecated and update usage. 2016-05-20 22:11:31 +02:00
example Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
handler Replace DomainMappingBuilder with DomainNameMappingBuilder 2016-05-18 12:03:14 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
license added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
microbench Introduce CodecOutputList to reduce overhead of encoder/decoder 2016-05-20 09:12:07 +02:00
resolver Change hosts file resolver to be case-insensitive 2016-05-10 08:57:48 +02:00
resolver-dns Do not send duplicate DNS queries when the same query is in progress already 2016-05-17 15:07:36 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
testsuite Add CompositeByteBuf.addComponent(boolean ...) method to simplify usage 2016-05-21 19:52:16 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
transport Add CompositeByteBuf.addComponent(boolean ...) method to simplify usage 2016-05-21 19:52:16 +02:00
transport-native-epoll DuplexChannel to support shutdownInput 2016-05-18 09:11:49 +02:00
transport-rxtx DuplexChannel to support shutdownInput 2016-05-18 09:11:49 +02:00
transport-sctp Make retained derived buffers recyclable 2016-05-17 11:16:13 +02:00
transport-udt DuplexChannel to support shutdownInput 2016-05-18 09:11:49 +02: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 Update tcnative version 2016-05-22 17:47:35 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +01:00
run-example.sh Add an example client for codec-redis 2016-04-23 11:18:12 -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

Development of all 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.