Go to file
Trustin Lee 550577d4da Enforce the release is performed only from RHEL 6.5 or equivalent
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.
2014-05-02 21:20:47 +09:00
all Enforce the release is performed only from RHEL 6.5 or equivalent 2014-05-02 21:20:47 +09:00
buffer [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
codec [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
codec-http [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
common Simplify native library resolution using os-maven-plugin 2014-05-02 04:22:11 +09:00
example [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
handler [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
license [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 11:44:06 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
transport [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
transport-native-epoll Simplify native library resolution using os-maven-plugin 2014-05-02 04:22:11 +09:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
.fbfilter.xml Update license headers 2012-06-04 13:31:44 -07:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Format and partially describe Gitignore 2013-12-10 07:04:38 +01: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 [#1259] Add optimized queue for SCMP pattern and use it in NIO and native transport 2014-02-27 11:44:06 +01:00
pom.xml Enforce the release is performed only from RHEL 6.5 or equivalent 2014-05-02 21:20:47 +09:00
README.md Update README.md 2014-01-16 14:38:36 +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

The 'master' branch is where the development of the latest major version lives on. The development of all other major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.