fa64625522
Motivation: Release 4.0.25 was not usable in OSGi environments due to a simple typo. An automated test could have caught the problem even before it was committed. Modifications: This patch introduces a new artifact, osgitests, which pulls in all production artifacts (which we want to be checked for OSGi compliance). It contains only a single unit test, which runs a pax-exam container with felix OSGi. At initialization time, it scans all the artifact's dependencies, looking for things belonging to io.netty group. The container is configured to deploy those artifacts as bundles and fail if any bundle is found to be unresolved. It performs a final check to see if any bundles were tested this way, to make sure the mechanism is not completely broken. We are using wrappedBundle(), as two of our third-party dependencies do not export packages correctly -- this masks the problem, assuming that whoever deploys our artifacts depending on them will figure out how to OSGify them. Result: Simple typos and other bundle manifest errors should be caught during test phase of every build. |
||
|---|---|---|
| all | ||
| buffer | ||
| codec | ||
| codec-dns | ||
| codec-haproxy | ||
| codec-http | ||
| codec-http2 | ||
| codec-memcache | ||
| codec-mqtt | ||
| codec-socks | ||
| codec-stomp | ||
| common | ||
| example | ||
| handler | ||
| handler-proxy | ||
| license | ||
| microbench | ||
| resolver | ||
| resolver-dns | ||
| tarball | ||
| testsuite | ||
| testsuite-osgi | ||
| transport | ||
| transport-native-epoll | ||
| transport-rxtx | ||
| transport-sctp | ||
| transport-udt | ||
| .fbprefs | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| pom.xml | ||
| README.md | ||
| run-example.sh | ||
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:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
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.