Go to file
Scott Mitchell b249714a2d DNS Resovler tests should be more explicit about ndots
Motivation:
The DNS resolver may use default configuration inherited from the environment. This means the ndots value may change and result in test failure if the tests don't explicitly set the assumed value.

Modifications:
- Explicitly set ndots in resolver-dns unit tests so we don't fail if the environment overrides the search domain and ndots

Result:
Unit tests are less dependent upon the enviroment they run in.
Fixes https://github.com/netty/netty/issues/6966.
2017-07-12 15:49:45 -07:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
bom [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
buffer SslHandler aggregation of plaintext data on write 2017-07-10 12:22:08 -07:00
codec [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-http Use ByteBuf#writeShort/writeMedium instead of writeBytes 2017-07-10 14:37:41 +02:00
codec-http2 [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-redis [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-smtp Use ByteBuf#writeShort/writeMedium instead of writeBytes 2017-07-10 14:37:41 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
common Use unbounded queues from JCTools 2.0.2 2017-07-10 12:32:15 -07:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
example [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
handler Fix Race in ReferenceCountedOpenSslEngine 2017-07-12 09:52:57 -07:00
handler-proxy HttpProxyHandler: allow setting headers 2017-07-06 20:02:06 +02:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
microbench Use ByteBuf#writeShort/writeMedium instead of writeBytes 2017-07-10 14:37:41 +02:00
resolver [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
resolver-dns DNS Resovler tests should be more explicit about ndots 2017-07-12 15:49:45 -07:00
tarball [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
transport Use unbounded queues from JCTools 2.0.2 2017-07-10 12:32:15 -07:00
transport-native-epoll Use unbounded queues from JCTools 2.0.2 2017-07-10 12:32:15 -07:00
transport-native-kqueue Use unbounded queues from JCTools 2.0.2 2017-07-10 12:32:15 -07:00
transport-native-unix-common [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-07-06 13:24:06 +02: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:19:45 +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
NOTICE.txt Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
pom.xml Use unbounded queues from JCTools 2.0.2 2017-07-10 12:32:15 -07:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +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.