Go to file
Nikolay Fedorovskikh 0623c6c533 Fix javadoc issues
Motivation:

Invalid javadoc in project

Modifications:

Fix it

Result:

More correct javadoc
2017-02-22 07:31:07 +01:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all Missing release modules in netty-all project 2017-02-20 13:44:36 +01:00
buffer Fix javadoc issues 2017-02-22 07:31:07 +01:00
codec Fix javadoc issues 2017-02-22 07:31:07 +01:00
codec-dns Prefer JDK ThreadLocalRandom implementation over ours. 2017-02-16 15:44:00 -08:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-01-30 15:14:02 +01:00
codec-http Fix javadoc issues 2017-02-22 07:31:07 +01:00
codec-http2 Fix javadoc issues 2017-02-22 07:31:07 +01:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-01-30 15:14:02 +01:00
codec-mqtt Introduced MqttMessageBuilders to fluently create MQTT messages 2017-02-19 13:39:59 +01:00
codec-redis Adding 'final' keyword for private fields where possible 2017-02-14 08:29:15 +01:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2017-01-30 15:14:02 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-01-30 15:14:02 +01:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2017-01-30 15:14:02 +01:00
codec-xml Fix some warnings at generics usage 2017-02-22 07:29:59 +01:00
common Fix javadoc issues 2017-02-22 07:31:07 +01:00
example Adding 'final' keyword for private fields where possible 2017-02-14 08:29:15 +01:00
handler Fix javadoc issues 2017-02-22 07:31:07 +01:00
handler-proxy Make netty build work on Java9 2017-02-16 20:26:30 +01:00
license added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
microbench Fix javadoc issues 2017-02-22 07:31:07 +01:00
resolver Fix some warnings at generics usage 2017-02-22 07:29:59 +01:00
resolver-dns Prefer JDK ThreadLocalRandom implementation over ours. 2017-02-16 15:44:00 -08:00
tarball [maven-release-plugin] prepare for next development iteration 2017-01-30 15:14:02 +01:00
testsuite Move AutobahnTestsuite to extra module 2017-02-21 10:13:31 +01:00
testsuite-autobahn Move AutobahnTestsuite to extra module 2017-02-21 10:13:31 +01:00
testsuite-osgi Make netty build work on Java9 2017-02-16 20:26:30 +01:00
transport Fix javadoc issues 2017-02-22 07:31:07 +01:00
transport-native-epoll Make netty build work on Java9 2017-02-16 20:26:30 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-01-30 15:14:02 +01:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-01-30 15:14:02 +01:00
transport-udt Fix javadoc issues 2017-02-22 07:31:07 +01: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 Update to netty-tcnative 2.0.0.Beta6 2017-02-21 15:55:57 +01: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.