[OpenNMS/opennms] 0a124c: NMS-20168: Update Netty to 4.2.16.Final

  Branch: refs/heads/mm/NMS-20168-smoke
  Home:   https://github.com/OpenNMS/opennms
  Commit: 0a124cd7c14564f7544421203dd1622f70cb25b3
      https://github.com/OpenNMS/opennms/commit/0a124cd7c14564f7544421203dd1622f70cb25b3
  Author: Marshall Massengill <[email protected]>
  Date:   2026-08-06 (Thu, 06 Aug 2026)

  Changed paths:
    M container/features/src/main/resources/features-core.xml
    M container/features/src/main/resources/features.xml
    M container/karaf/src/main/filtered-resources/etc/overrides.properties
    M container/shared/src/main/filtered-resources/etc/overrides.properties
    M pom.xml
    M smoke-test/pom.xml

  Log Message:
  -----------
  NMS-20168: Update Netty to 4.2.16.Final

Moves foundation-2023 onto the 4.2 line rather than the last 4.1 release,
matching foundation-2024 and later. 4.1.x still receives fixes, but the
advisory backlog is being closed on 4.2, and staying on 4.1 means diverging
from every downstream branch.

Netty 4.2 turned netty-codec into a class-free aggregate and moved its
contents into netty-codec-base, -compression, -protobuf and -marshalling.
Bundles importing io.netty.handler.codec* therefore lose their provider, so
the Karaf features and both overrides.properties gain netty-codec-base, and
netty-codec-compression wherever netty-codec-http is installed (it imports
io.netty.handler.codec.compression unconditionally). netty-codec-xml and its
aalto-xml dependency are declared explicitly for XmlFrameDecoderFactory,
which no longer reaches the XML codec through netty-codec.

No Java changes are needed: the netty surface used here is ByteBuf,
bootstraps and stock handlers, and the deprecated-in-4.2 pieces still in use
(NioEventLoopGroup, DefaultEventLoopGroup, SocketUtils, the resolver.dns
cache types) all still ship in 4.2.16. gRPC is grpc-netty-shaded throughout,
so it is unaffected, and camel-netty4 imports netty packages without a
version range.

The smoke-test reactor moves to the same version so the tests run against the
netty the product ships; it imports netty-bom, so the split codec modules
follow without further declarations.

Two 4.2 defaults changed and may need pinning if a deployment depends on the
old behaviour: the allocator is now adaptive rather than pooled
(io.netty.allocator.type=pooled) and netty client TLS verifies hostnames
(io.netty.handler.ssl.defaultEndpointVerificationAlgorithm=NONE).



To unsubscribe from these emails, change your notification settings at https://github.com/OpenNMS/opennms/settings/notifications


_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/wiki/index.php?page=MailingListFaq
opennms-cvs mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-cvs