Go to file
Scott Mitchell 23f881b382 Comment punctuation cleanup
Motivation:
Commit d857b16d76 introduced some comments that had no punctuation.

Modifications:
Add punctuation.

Result:
Comments have punctuation.
2015-03-26 13:01:37 -07:00
all HTTP/2 codec missing from all/pom.xml 2015-03-23 16:29:28 -07:00
buffer Updates the javadoc of Unpooled to remove mention to methods it does not provide 2015-03-04 12:04:14 +09:00
codec Add support for byte order to LengthFieldPrepender 2015-03-13 18:50:20 +01:00
codec-dns [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
codec-http Fix example in CookieDecoder Javadoc 2015-03-26 11:48:51 +09:00
codec-http2 Comment punctuation cleanup 2015-03-26 13:01:37 -07:00
codec-memcache Returns after encoding each message not do check following instance types 2015-03-19 20:43:59 +01:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
codec-socks Hide password in exception messages of SocksAuthRequest 2015-03-17 17:25:09 +09:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
common Respect -Djava.net.preferIPv4Stack when using epoll transport 2015-03-11 02:50:11 +01:00
example Using public LogLevel for HTTP/2 frame logging. 2015-03-17 15:10:35 -07:00
handler Using public LogLevel for HTTP/2 frame logging. 2015-03-17 15:10:35 -07:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
license Integrate non-blocking XML parser as Netty codec (#2806) 2015-02-19 13:46:14 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
resolver Use InetSocketAddress.getHostName() instead of getHostString() 2015-03-10 11:49:23 +09:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
tarball [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
transport Small typos fixes in Channel's Javadoc 2015-03-21 16:10:24 +01:00
transport-native-epoll First load RuntimeException to prevent segfault on error 2015-03-13 18:28:40 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-03-03 02:06:47 -05: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:36:54 +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:13: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 13:46:14 +01:00
pom.xml Jetty ALNPN and NPN updates plus backport 2015-03-25 08:55:52 -07:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:24 -07:00
run-example.sh HTTP/2 examples run script support 2015-03-23 16:27:55 -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

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.