<?xml version="1.0" encoding="UTF-8"?>
<!--
  ~ Copyright The WildFly Authors
  ~ SPDX-License-Identifier: Apache-2.0
  -->
<module name="io.netty.netty-common" xmlns="urn:jboss:module:1.9">
    <properties>
        <property name="jboss.api" value="private"/>
    </properties>

    <resources>
        <artifact name="io.netty:netty-common:4.1.116.Final"/>
    </resources>

    <dependencies>
        <module name="java.logging"/>
        <module name="jdk.unsupported"/>
        <module name="io.netty.netty-transport-native-unix-common"/>
        <module name="io.netty.netty-transport-native-epoll"/>
        <module name="io.netty.netty-transport-native-kqueue"/>
        <!-- 
            There is no requirement for this in Netty. This avoids a warning from
            JBoss Modules which gets logged when checking the InternalLoggerFactory
            for which logging framework to bind to. Netty isn't aggressive enough
            when attempting to see if log4j 2 is available and JBoss Modules
            is a bit too aggressive with logging the warning. For this reason
            it is best to just process through log4j 2.
            @see https://issues.redhat.com/browse/WFLY-20058
        -->
        <module name="org.apache.logging.log4j.api"/>
    </dependencies>
</module>
