Build 3.1.2 contains several new artifacts[1] from quarkus-apicurio group, brought in by quarkus-apicurio-registry-avro extension. None of them is supported in product, but they depend on (and bring into the resulting zip) artifact io/quarkus/quarkus-bom/2.13.7.Final-redhat-00003.

Between Quarkus 2.13 and 3.0 there was an incompatible change from javax to jakarta, so we prefer to not have these two quarkus boms on classpath. Is it possible to not include/productize apicurio-registry and, therefore, not include 2.13 quarkus-bom into the build?

[1] https://main-jenkins-csb-quarkusqe.apps.ocp-c1.prod.psi.redhat.com/view/all/job/rhbq-platform-quarkus-maven-repo-gav-diff/8/artifact/artifacts_3.1.2.ER1_ADDED.txt/*view*/