f86356f083
Motivation: So far, we generated and deployed test JARs to Maven repositories. The deployed JAR had the classifier 'test-jar'. The test JAR is consumed by transport-native-epoll as a test dependency. The problem is, when netty-transport-native-epoll pulls the test JAR as a dependency, that Maven resolves its transitive dependencies at 'compile' and 'runtime' scope only, which is incorrect. I was bitten by this problem recently while trying to add a new dependency to netty-testsuite. Because I added a new dependency at the 'test' scope, the new dependency was not pulled transitively by transport-native-epoll and caused an unexpected build failure. - d6160208c37cfd21b690f1a0df67776bf986b28e - bf77bb4c3ae04778e65b8a38c2a9ec0e15207de8 Modifications: - Move all classes in netty-testsuite from src/test to src/main - Update the 'compile' scope dependencies of netty-testsuite - Override the test directory configuration properties of the surefire plugin - Do not generate the test JAR anymore - Update the dependency of netty-transport-native-epoll Result: It is less error-prone to add a new dependency to netty-testsuite.
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 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.