724aed4757
Motivation: oss.sonatype.org refuses to promote an artifact if it doesn't have the default JAR (the JAR without classifier.) Modifications: - Generate both the default JAR and the native JAR to make oss.sonatype.org happy - Rename the profile 'release' to 'restricted-release' which reflects what it really does better - Remove the redundant <quickbuild>true</quickbuild> in all/pom.xml We specify the profile 'full' that triggers that property already in maven-release-plugin configuration. Result: oss.sonatype.org is happy. Simpler pom.xml |
||
---|---|---|
all | ||
buffer | ||
codec | ||
codec-http | ||
codec-http2 | ||
codec-memcache | ||
codec-socks | ||
common | ||
example | ||
handler | ||
license | ||
microbench | ||
tarball | ||
testsuite | ||
transport | ||
transport-native-epoll | ||
transport-rxtx | ||
transport-sctp | ||
transport-udt | ||
.fbfilter.xml | ||
.fbprefs | ||
.gitignore | ||
.travis.yml | ||
CONTRIBUTING.md | ||
LICENSE.txt | ||
NOTICE.txt | ||
pom.xml | ||
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:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
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.