AnnJoy23 opened a new pull request, #7113: URL: https://github.com/apache/incubator-kie/pull/7113
## Summary quarkus-bom 3.33.3.2 ships netty 4.1.136.Final. Without an explicit `netty-bom` import ahead of it, `netty-transport-native-unix-common` (not listed in `kie-parent`'s explicit managed entries) resolves at 4.1.136.Final even though other netty artifacts are explicitly managed at 4.1.137.Final. This PR adds a `netty-bom` import at `4.1.137.Final` **before** `quarkus-bom` in the three independent Quarkus BOM roots so that all Quarkus trees (kogito, kie, optaplanner) consistently resolve netty at `4.1.137.Final`. It also bumps `version.io.vertx` from `4.5.31` to `4.5.32` in `kie-parent` — `vertx-dependencies:4.5.32` aligns its internal `netty.version` to `4.1.137.Final`. Maven import BOM resolution rule: **first import wins**. The `netty-bom` import must remain **before** `quarkus-bom` in all three files — a reordering is a functional regression. Files **not** changed (by design): - `kogito-springboot/bom/pom.xml` — Spring Boot tree uses netty 4.2.x; already has its own netty pin ## Changes | File | Change | |------|--------| | `kie-parent/pom.xml` | bumped `version.io.vertx` 4.5.31 → 4.5.32 | | `kie-quarkus-build-parent/pom.xml` | added `version.io.netty=4.1.137.Final` property; inserted `netty-bom` import before `quarkus-bom` | | `kogito-quarkus/bom/pom.xml` | added `version.io.netty=4.1.137.Final` property; inserted `netty-bom` import before `quarkus-bom` | | `optaplanner-build/optaplanner-build-parent/pom.xml` | added `version.io.netty=4.1.137.Final` property; inserted `netty-bom` import before `quarkus-bom` | -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
