I am just trying to enhance bacon pig to be able to generate the MRRC zip based on the content of a BOM (instead of having to provide an external extensionsListUrl). The idea is to go through the BOM (camel-quarkus-bom in my case), filter artifacts having a redhat- version and use that list as an input for the RESOLVE_ONLY strategy of pig.

When doing that for `org.apache.camel.quarkus:camel-quarkus-bom:2.2.1.fuse-800015-redhat-00001` which imports `io.quarkus:quarkus-bom:2.2.5.Final-redhat-00010` I found out there is a couple of artifacts managed in `io.quarkus:quarkus-bom:2.2.5.Final-redhat-00010` that do not exist:

io.netty:netty-transport-native-unix-common:osx-aarch_64:4.1.69.Final-redhat-00001
io.netty:netty-transport-native-unix-common:osx-x86_64:4.1.69.Final-redhat-00001
io.netty:netty-transport-native-unix-common:linux-aarch_64:4.1.69.Final-redhat-00001
io.netty:netty-transport-native-epoll:linux-aarch_64:4.1.69.Final-redhat-00001

The community version 4.1.69.Final exists for these and io.quarkus:quarkus-bom should thus manage them at that version.

Note that this issue does not exist for netty-transport-native-kqueue which is properly managed at 4.1.69.Final.

The following are similar: jars are managed, but only poms exist:

io.smallrye.reactive:vertx-mutiny-clients:jar:2.13.0.redhat-00009
io.vertx:vertx-sql-client-parent:jar:4.1.8.redhat-00003
io.vertx:vertx-grpc-parent:jar:4.1.8.redhat-00003

client.js does not seem to exist at all since 4.0.0 (it used to exist till 3.9.9)

io.vertx:vertx-web:js:client:4.1.8.redhat-00003