Go to file
Norman Maurer 06c629a226 PooledByteBuf.capacity(...) not enforces maxCapacity()
Motivation:

PooledByteBuf.capacity(...) miss to enforce maxCapacity() and so its possible to increase the capacity of the buffer even if it will be bigger then maxCapacity().

Modifications:

- Correctly enforce maxCapacity()
- Add unit tests for capacity(...) calls.

Result:

Correctly enforce maxCapacity().
2017-02-01 18:48:20 +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-30 17:42:39 +01:00
buffer PooledByteBuf.capacity(...) not enforces maxCapacity() 2017-02-01 18:48:20 +01:00
codec [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
codec-http [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
common [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
example [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
handler [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
testsuite [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
transport [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +01:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +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 [maven-release-plugin] prepare for next development iteration 2017-01-30 17:42:39 +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

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.