Go to file
Trustin Lee 4aa10db9c5 Use InetSocketAddress.getHostName() instead of getHostString()
Related: #3478

Motivation:

DefaultNameResolver uses InetSocketAddress.getHostString() instead of
getHostName(). Because Netty uses the DefaultNameResolver by default and
getHostString() is available only since Java 7, a user cannot use Netty
on Java 6 anymore.

Modifications:

Use InetSocketAddress.getHostName() which is practically same and also
is available in Java 6.

Result:

Netty 4.1 runs on Java 6 again.
2015-03-10 11:45:56 +09:00
all [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
buffer Updates the javadoc of Unpooled to remove mention to methods it does not provide 2015-03-04 12:04:27 +09:00
codec Add unit to maxContentLength message javadoc 2015-03-05 20:47:51 +01:00
codec-dns [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
codec-http Add unit to maxContentLength javadoc of HttpObjectAggregator 2015-03-05 20:47:51 +01:00
codec-http2 [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
common [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
example [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
handler Add a new constructor without handler parameter to TrafficCounter 2015-03-10 11:28:41 +09:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
license Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 14:17:17 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
resolver Use InetSocketAddress.getHostName() instead of getHostString() 2015-03-10 11:45:56 +09:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
tarball [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
transport Fix SocketException in NioSocketChannelUnsafe.closeExecutor() 2015-03-05 15:18:27 +09:00
transport-native-epoll Fix redundancy in javadocs 2015-03-10 00:08:41 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Exclude bin directory from git Motivation: 2014-08-27 06:33:22 +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:17:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 14:17:17 +01:00
pom.xml [maven-release-plugin] prepare for next development iteration 2015-03-03 08:30:59 -05:00
README.md Add a link to the 'native transports' page 2014-07-21 12:10:16 -07:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:49:27 +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 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.