Major RHBK appears to depend on some dependencies managed by the quarkus-bom that are unaligned (reset to their original upstream versions) during productization of RHBQ.
These dependencies include:
- io.netty:netty-all:4.1.108.Final (BOM entry)
- com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:2.17.0 (BOM entry, dependency of quarkus-amazon-lambda-xray)
- info.picocli:picocli:4.7.5 (BOM entry, dependency of quarkus-picocli)
The Netty and Jackson ones are imported with the corresponding BOM imports but are unaligned since no supported extension in RHBQ needs those.
io.quarkus:quarkus-jdbc-h2-deployment:3.8.5
io.quarkus:quarkus-jdbc-h2:3.8.5
This extension is actually productized but unaligned. It's not a supported extension.
net.java.dev.jna:jna:5.8.0
net.java.dev.jna:jna-platform:5.8.0
These artifacts are excluded from our dependency analysis and unaligned since, afaiu, they require a special effort to rebuild? But they are still shipped productized as part of RHBK. Perhaps we should review a decision on this one.
Besides discussing these specific dependencies, there is an option to automatically include RHBK dependencies managed by Quarkus in the depsToBuild report the same way it's done for other layered products, such as Camel Quarkus, AMQ Qpid JMS client, QOSDK, etc. The following commit would do that https://gitlab.cee.redhat.com/olubyans/quarkus-platform/-/commit/ea0e93c1e0036e82be431e62b867462f465f0a94
