Go to file
Scott Mitchell 74da4c54bc NativeLibraryLoader logging clarify
Motivation:
NativeLibraryLoader may only log a debug statement if the library is successfully loaded from java.library.path, but will log failure statements the if load for java.library.path fails which can mislead users to believe the load actually failed when it may have succeeded.

Modifications:
- Always load a debug statement when a library was successfully loaded

Result:
NativeLibraryLoader log statements more clear.
2017-09-15 09:18:00 -07:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:46 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-08-24 12:47:31 +00:00
bom [maven-release-plugin] prepare for next development iteration 2017-08-24 12:47:31 +00:00
buffer Enable PooledByteBufAllocator to work, event without a cache 2017-09-08 10:21:05 +02:00
codec Makes LengthFieldBasedFrameDecoder::decode inlineable 2017-08-28 09:09:00 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-08-24 12:47:31 +00:00
codec-http HttpObjectEncoder buffer size estimation 2017-08-31 11:24:27 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-08-24 12:47:31 +00:00
common NativeLibraryLoader logging clarify 2017-09-15 09:18:00 -07:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-08-24 12:47:31 +00:00
example [maven-release-plugin] prepare for next development iteration 2017-08-24 12:47:31 +00:00
handler Only load native transport if running architecture match the compiled library architecture. 2017-09-04 14:12:16 +02:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:32:36 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2017-08-24 12:47:31 +00:00
tarball [maven-release-plugin] prepare for next development iteration 2017-08-24 12:47:31 +00:00
testsuite [maven-release-plugin] prepare for next development iteration 2017-08-24 12:47:31 +00:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-08-24 12:47:31 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-08-24 12:47:31 +00:00
transport AutoClose behavior may infinite loop 2017-08-25 22:57:32 -07:00
transport-native-epoll Use the correct osname in the Bundle-NativeCode declaration. 2017-09-14 08:30:13 -07:00
transport-native-kqueue/src/test/java/io/netty/channel/kqueue Correctly handle connect/disconnect in EpollDatagramChannel 2017-08-04 10:47:05 +02:00
transport-rxtx Mark transport-rxtx as @deprecated 2017-09-14 09:43:38 -07:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-08-24 12:47:31 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-08-24 12:47:31 +00: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:53:28 +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:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:32:36 +01:00
pom.xml [maven-release-plugin] prepare for next development iteration 2017-08-24 12:47:31 +00:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:09:30 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:50:53 +02: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.