andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
7,140 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
0d2a0abaa2
Go to file
Norman Maurer 0d2a0abaa2 Ensure tests added in 91f050d2ef work with different openssl installations 
Motivation:

Tests were added in 91f050d2ef to run with different protocols / ciphers. These may fail currently when openssl was compiled without support for the protocol / ciphers.

Modifications:

- Refactor tests to easier understand for which protocol / cipher it failed
- Not fail the test if the protocol is not supported with the used openssl version.

Result:

More robust testing.
2017-01-30 13:22:11 +01: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-01-12 13:25:14 +01:00
buffer Calculate correct count for tiny/small/normal allocation 2017-01-30 10:34:12 +01:00
codec [maven-release-plugin] prepare for next development iteration 2017-01-12 13:25:14 +01:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-01-12 13:25:14 +01:00
codec-http Set the Transfer-Encoding header instead of adding 2017-01-25 07:59:19 +01:00
codec-socks Wrap operations requiring SocketPermission with doPrivileged blocks 2017-01-19 21:23:28 +01:00
common Wrap operations requiring SocketPermission with doPrivileged blocks 2017-01-19 21:23:28 +01:00
example Wrap operations requiring SocketPermission with doPrivileged blocks 2017-01-19 21:23:28 +01:00
handler Ensure tests added in 91f050d2ef work with different openssl installations 2017-01-30 13:22:11 +01:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench Wrap operations requiring SocketPermission with doPrivileged blocks 2017-01-19 21:23:28 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2017-01-12 13:25:14 +01:00
testsuite Wrap operations requiring SocketPermission with doPrivileged blocks 2017-01-19 21:23:28 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-01-12 13:25:14 +01:00
transport Wrap operations requiring SocketPermission with doPrivileged blocks 2017-01-19 21:23:28 +01:00
transport-native-epoll Check if Epoll is avaible when construct EpollEventLoopGroup 2017-01-27 08:21:36 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-01-12 13:25:14 +01:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-01-12 13:25:14 +01:00
transport-udt Wrap operations requiring SocketPermission with doPrivileged blocks 2017-01-19 21:23:28 +01: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 Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
pom.xml Update jetty-alpn-agent to support latest JDK releases. 2017-01-26 12:18:58 +01: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 logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +09:00

README.md

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

Links

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.