Go to file
radai-rosenblatt 15ac6c4a1f Clean-up unused imports
Motivation:

the build doesnt seem to enforce this, so they piled up

Modifications:

removed unused import lines

Result:

less unused imports

Signed-off-by: radai-rosenblatt <radai.rosenblatt@gmail.com>
2016-09-30 09:08:50 +02:00
all [maven-release-plugin] prepare for next development iteration 2016-08-26 10:06:32 +02:00
buffer Clean-up unused imports 2016-09-30 09:08:50 +02:00
codec Clean-up unused imports 2016-09-30 09:08:50 +02:00
codec-dns Clean-up unused imports 2016-09-30 09:08:50 +02:00
codec-haproxy This PR fixes an issue with the PROXY protocol where the reader index of a consumed byte array was not set correctly. 2016-09-29 21:21:01 +02:00
codec-http Clean-up unused imports 2016-09-30 09:08:50 +02:00
codec-http2 Clean-up unused imports 2016-09-30 09:08:50 +02:00
codec-memcache Clean-up unused imports 2016-09-30 09:08:50 +02:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2016-08-26 10:06:32 +02:00
codec-redis [maven-release-plugin] prepare for next development iteration 2016-08-26 10:06:32 +02:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2016-08-26 10:06:32 +02:00
codec-socks NetUtil.bytesToIpAddress bug 2016-09-22 17:06:21 -07:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2016-08-26 10:06:32 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2016-08-26 10:06:32 +02:00
common Clean-up unused imports 2016-09-30 09:08:50 +02:00
example Fix IndexOutOfBoundsException in HelloWorldHttp2Handler 2016-09-16 16:21:53 -07:00
handler Clean-up unused imports 2016-09-30 09:08:50 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2016-08-26 10:06:32 +02:00
license added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
microbench Clean-up unused imports 2016-09-30 09:08:50 +02:00
resolver [maven-release-plugin] prepare for next development iteration 2016-08-26 10:06:32 +02:00
resolver-dns Add support for Client Subnet in DNS Queries (RFC7871) 2016-09-06 07:16:57 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-08-26 10:06:32 +02:00
testsuite Clean-up unused imports 2016-09-30 09:08:50 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-08-26 10:06:32 +02:00
transport Clean-up unused imports 2016-09-30 09:08:50 +02:00
transport-native-epoll [#5800] Support any FileRegion implementation when using epoll transport 2016-09-15 23:03:37 -07:00
transport-rxtx Remove @Deprecated for primitive WriteWaterMark getters and setters 2016-09-05 10:26:05 +02:00
transport-sctp Improve SctpMessageCompletionHandler 2016-09-19 08:23:00 -07:00
transport-udt Clean-up unused imports 2016-09-30 09:08:50 +02:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02: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 Fix typo for max leak records system property 2016-09-21 23:15:27 -07: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.