a566164b98
Motivation: Netty must be released from RHEL 6.5 x86_64 or compatible so that: 1) we ship x86_64 version of epoll transport officially, and 2) we ensure the ABI compatibility with older GLIBC versions. The shared library built on a distribution with newer GLIBC will not run on older distributions. Modifications: - When 'release' profile is active, perform an additional check using maven-enforcer-plugin so that 'mvn release:*' fails when running on non-RHEL6.5. This rule is active only when releasing, so a user should not be affected. - Simplify maven-release-plugin configuration by removing redundant profiles such as 'linux'. 'linux' is automatically activated when releasing because we now enforce the release occurs on linux-x86_64. - Remove the no-osgi profile, which is unused - Remove the reference to 'sonatype-oss-release' profile in all/pom.xml, because we always specify 'release' profile when releasing - Rename the profile 'linux-native' to 'linux' for brevity - Upgrade oss-parent and maven-enforcer-plugin Result: No one can make a mistake to release Netty on an environment that can produce incompatible or missing native library.
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.