The native transports wiki page suggests using the os-maven-plugin maven plugin to configure the classifier of e.g. the netty-transport-native-epoll dependency.

But this will substitute the os name and arch based on the build environment, which would typically be arbitrary/variable (e.g. a CI platform, local workstation, ...). Whereas this is only really important for the target runtime environment.

Furthermore, only linux-x86_64 is supported for epoll, and so it seems to me the correct advice would be to have the <classifier> fixed to this wherever the dependency is included, regardless of the build/runtime envs. This is effectively what happens already when using netty-all.