History

Trustin Lee 2668944e0b Generate non-test JAR for netty-testsuite 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. - `d6160208c3` - `bf77bb4c3a` 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.		2014-12-15 09:17:51 +09:00
..
src	Remove bottleneck while create InetSocketAddress in native transport	2014-12-12 18:23:18 +01:00
pom.xml	Generate non-test JAR for netty-testsuite	2014-12-15 09:17:51 +09:00
README.md	Introduce a native transport for linux using epoll ET	2014-02-15 22:42:07 +01:00

Native transport for Linux