Commit Graph

11 Commits

Author SHA1 Message Date
Andrea Cavalli
219bbd44dc Rename package 2021-09-17 16:28:15 +02:00
Norman Maurer
05f79e9e45 [maven-release-plugin] prepare for next development iteration 2021-03-19 09:57:50 +01:00
Norman Maurer
3048744436 [maven-release-plugin] prepare release netty-build-29 2021-03-19 09:57:45 +01:00
Chris Vest
51248ba58f Make checkstyle ignore module-info.java files
Checkstyle cannot yet parse these files, so we have to make it ignore them.
2021-03-18 11:47:30 +01:00
Norman Maurer
b1ce81f888 [maven-release-plugin] prepare for next development iteration 2020-11-06 07:51:30 +01:00
Norman Maurer
c2c0aef2b7 [maven-release-plugin] prepare release netty-build-28 2020-11-06 07:51:22 +01:00
Norman Maurer
62f3b989cb Fix location of xml files 2020-11-06 07:49:21 +01:00
Norman Maurer
d470fe9b49 [maven-release-plugin] prepare for next development iteration 2020-11-05 15:59:52 +01:00
Norman Maurer
d1dbd3108f [maven-release-plugin] prepare release netty-build-27 2020-11-05 15:59:44 +01:00
Norman Maurer
7e00129e61 Rename artifacts 2020-11-05 15:56:18 +01:00
Norman Maurer
af09be8634
Introduce maven plugin that can check that a native lib can be used w… (#10)
Motivation:

In the past we messed up released native libs as we did compile on the wrong GLIBC version. This can lead to situations when its not possible anymore to use the native libs an a specific system. We should be able to verify that all works as expected during the build / release process.

Modifications:

- Make netty-build a multi maven module project
- Move all existing code to the common module
- Introduce glibccheck-maven-plugin that can be used to validate that a native lib will be usable with a specific GLIBC version

Result:

Provide maven plugin that can be used to verify linking of native lib to correct GLIBC version
2020-11-05 13:55:43 +01:00