Go to file
Trustin Lee f0a4802d1f Do not log CNFE when tcnative is not in classpath
Motivation:

When a user deliberatively omitted netty-tcnative from classpath, he or
she will see an ugly stack trace of ClassNotFoundException.

Modifications:

Log more briefly when netty-tcnative is not in classpath.

Result:

Better-looking log at DEBUG level
2015-01-08 12:25:31 +09:00
all [maven-release-plugin] prepare for next development iteration 2014-12-31 20:58:44 +09:00
buffer [maven-release-plugin] prepare for next development iteration 2014-12-31 20:58:44 +09:00
codec [maven-release-plugin] prepare for next development iteration 2014-12-31 20:58:44 +09:00
codec-http Fix for Issue #3308 related to slice missing retain 2015-01-06 17:31:33 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-12-31 20:58:44 +09:00
common [maven-release-plugin] prepare for next development iteration 2014-12-31 20:58:44 +09:00
example [maven-release-plugin] prepare for next development iteration 2014-12-31 20:58:44 +09:00
handler Do not log CNFE when tcnative is not in classpath 2015-01-08 12:25:31 +09:00
license Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2014-12-31 20:58:44 +09:00
tarball [maven-release-plugin] prepare for next development iteration 2014-12-31 20:58:44 +09:00
testsuite [maven-release-plugin] prepare for next development iteration 2014-12-31 20:58:44 +09:00
transport [maven-release-plugin] prepare for next development iteration 2014-12-31 20:58:44 +09:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2014-12-31 20:58:44 +09:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-12-31 20:58:44 +09:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-12-31 20:58:44 +09:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-12-31 20:58:44 +09: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:37:12 +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:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
pom.xml Fix broken OSGi version range for NPN and ALPN dependency 2015-01-03 11:51:12 +09:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +09: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 major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.