-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
-
https://github.com/debezium/debezium/pull/5640, https://github.com/debezium/debezium-server/pull/101, https://github.com/debezium/debezium-connector-jdbc/pull/83, https://github.com/debezium/debezium-connector-vitess/pull/200, https://github.com/debezium/debezium-connector-informix/pull/55, https://github.com/debezium/debezium-connector-spanner/pull/88, https://github.com/debezium/debezium-connector-ibmi/pull/19, https://github.com/debezium/debezium-connector-db2/pull/155, https://github.com/debezium/debezium-connector-cassandra/pull/130, https://github.com/debezium/debezium-operator/pull/63
-
-
There is an ongoing discussion in the Quarkus community to move to a requirement that any Quarkus project will require a minimum of Apache Maven 3.9.6 starting with 3.13+.
The rational behind this move is related to the fact that Maven prior to 3.9.6 used Eclipse Sisu 0.3.5, which uses an older version of ASM to read bytecode up to Java 14. If Maven plugins are compiled with newer versions of Java and support Sisu, the plugin could fail because the class reader fails to read the bytecode if the plugin baseline is Java 17.
Maven 3.9.6/3.97 uses Eclipse Sisu 0.9.0.M2, using ASM 9.5 to support up to Java 21 bytecode.
Maven 3.9.8 uses Eclipse Sisu 0.9.0.M3, using ASM 9.7 to support up to Java 23 bytecode.
At any rate, our wrapper is using 3.8.4, which is quickly approaching 3 years old.