Go to file
Norman Maurer 9bf74a6809
Update to netty-tcnative 2.0.12.Final (#8073)
Motivation:

A new version of tcnative was released that allows to use features depending on the runtime version of openssl, which makes it possible to use KeyManagerFactory and hostname verification on newer versions of centos/fedora/rhel and debian/ubuntu without the need to compile again.

Modifications:

Update to 2.0.12.Final

Result:

Use latest version of netty-tcnative to support more features.
2018-06-28 08:42:44 +02:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
.mvn/wrapper Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
all [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
bom [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
buffer Remove usage of ObjectCleaner (#8064) 2018-06-28 08:15:27 +02:00
codec Fix CharSequenceValueConverter.convertToByte implementation for AsciiString (#7994) 2018-06-01 21:15:08 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-http Fix random number generators in WebSocketUtil 2018-06-25 14:42:59 +02:00
codec-http2 Reorder channel state changes in Http2MultiplexCodec child channel 2018-06-28 08:10:54 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-xml [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
common Remove usage of ObjectCleaner (#8064) 2018-06-28 08:15:27 +02:00
dev-tools [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
docker Update to java 11+ea19 2018-06-25 16:47:01 +02:00
example We should re-use the same handler instance as its sharable in the example 2018-05-30 09:09:18 +02:00
handler OpenSSL (and so netty-tcnative) should allow to use custom engine. (#8050) 2018-06-28 08:13:52 +02:00
handler-proxy Get rid of deprecated SslContext methods in handler-proxy tests 2018-06-25 20:23:11 +02:00
license Add the NOTICE of the forked portion of Apache Harmony 2018-01-30 11:22:51 +01:00
microbench Including the setup code in the benchmark method to avoid JMH Invocation level hiccups. 2018-06-21 12:22:13 +02:00
resolver Check if Log level is enabled before creating log statements (#8022) 2018-06-13 23:21:53 -07:00
resolver-dns Remove id from DnsQueryContextManager whenever the promise is fullfilled. 2018-06-27 10:20:59 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
testsuite Revert "Ignore some test-flakiness when using Java11+ due outstanding Java11 bug. (#7984)" (#8035) 2018-06-19 08:11:10 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
testsuite-http2 [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
transport Expose channel count for FixedChannelPool (#8059) 2018-06-28 08:12:26 +02:00
transport-native-epoll Store NativeDatagramPacketArray directly in the EpollEventLoop 2018-06-27 20:52:28 +02:00
transport-native-kqueue Epoll and Kqueue shouldn't read by default (#8024) 2018-06-15 10:28:50 +02:00
transport-native-unix-common [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
transport-native-unix-common-tests Read until all data is consumed when EOF is detected even if readPend… (#7961) 2018-05-24 20:29:29 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
transport-sctp Check if Log level is enabled before creating log statements (#8022) 2018-06-13 23:21:53 -07:00
transport-udt [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitattributes Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
.gitignore Add docker-sync files to .gitignore 2018-05-15 10:39:14 +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
mvnw Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
mvnw.cmd Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
NOTICE.txt Add the NOTICE of the forked portion of Apache Harmony 2018-01-30 11:22:51 +01:00
pom.xml Update to netty-tcnative 2.0.12.Final (#8073) 2018-06-28 08:42:44 +02:00
README.md Provide an Automatic-Module-Name for the netty-all artifact fixes #7644 2018-01-27 20:31:16 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:41:07 +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.

Usage with JDK 9

Netty can be used in modular JDK9 applications as a collection of automatic modules. The module names follow the reverse-DNS style, and are derived from subproject names rather than root packages due to historical reasons. They are listed below:

  • io.netty.all
  • io.netty.buffer
  • io.netty.codec
  • io.netty.codec.dns
  • io.netty.codec.haproxy
  • io.netty.codec.http
  • io.netty.codec.http2
  • io.netty.codec.memcache
  • io.netty.codec.mqtt
  • io.netty.codec.redis
  • io.netty.codec.smtp
  • io.netty.codec.socks
  • io.netty.codec.stomp
  • io.netty.codec.xml
  • io.netty.common
  • io.netty.handler
  • io.netty.handler.proxy
  • io.netty.resolver
  • io.netty.resolver.dns
  • io.netty.transport
  • io.netty.transport.epoll (native omitted - reserved keyword in Java)
  • io.netty.transport.kqueue (native omitted - reserved keyword in Java)
  • io.netty.transport.unix.common (native omitted - reserved keyword in Java)
  • io.netty.transport.rxtx
  • io.netty.transport.sctp
  • io.netty.transport.udt

Automatic modules do not provide any means to declare dependencies, so you need to list each used module separately in your module-info file.