Go to file
Scott Mitchell b17ee6066f HTTP/2 Log Cleanup
Motivation:
The format of some log lines used the printf style formatting instead of the logger {} formatting for variables. This would lead to printing out the literal printf tokens instead of substituting the value.

Modifications:
- Fix the format string for log statements which use printf style formatting

Result:
Logs actually capture the value of the variables instead of fixed string tokens.
2016-05-06 10:52:00 -07:00
all [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
buffer Add CharSequence operations to ByteBuf 2016-05-06 16:52:00 +02:00
codec Add CharSequence operations to ByteBuf 2016-05-06 16:52:00 +02:00
codec-dns Update dependencies 2016-04-14 11:05:53 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
codec-http [#5202] Correctly throw ErrorDataDecoderException when invalid encoded form parameters are present. 2016-05-04 21:14:53 +02:00
codec-http2 HTTP/2 Log Cleanup 2016-05-06 10:52:00 -07:00
codec-memcache Add regression tests for FullMemcacheMessageRequest and FullMemcacheMessageResponse 2016-05-03 08:41:30 +02:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
codec-redis [#5190] Ensure memory is not leaked when readEndOfLine(...) throws an exception. 2016-05-06 07:45:44 +02:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
codec-xml Update dependencies 2016-04-14 11:05:53 +02:00
common [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
example Updating allowNullOrigin to return 'null' instead of '*'. 2016-05-03 08:39:38 +02:00
handler FlowControlHandlerTest invalid condition 2016-05-05 22:57:54 -07: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 Update dependencies 2016-04-14 11:05:53 +02:00
resolver [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
transport [#5171] Ensure NioDatagramChannelConfig can be instanced on android 2016-05-06 08:04:36 +02:00
transport-native-epoll EpollEventLoopGroup support Executor 2016-04-21 08:33:49 -07:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-04-10 08:37:18 +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 dependencies 2016-04-14 11:05:53 +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.