Mismatch between registry data and platform json bom for some extensions

[holly-cummins]

The problem

See original discussion on #41476

For two extensions, Websockets Next and Confluent Schema Registry - Avro, there is a mismatch between what ends up in the registry and what ends up in the platform bom json, target/quarkus-bom-quarkus-platform-descriptor-999-SNAPSHOT-999-SNAPSHOT.json.

The registry has un-enriched metadata, so it's missing things like the description from the pom.

The visible symptom

You can see the effect of this on extensions.quarkus.io:

http://code.quarkus.io has the correct descriptions for these extensions, even though the registry returns incorrect data. I think that's because code.quarkus is reading the platform bom json, rather than the registry entries for the extensions.

Why is this happening?

Um, not sure.

When websockets-next is built, the 'source' pom is in runtime/pom.xml, but the generated extension yaml ends up in server/target/runtime/quarkus-extension.yaml. I think ./runtime/target/classes/META-INF/quarkus-extension.yaml is what's used for the registry upload, but ./server/runtime/target/classes/META-INF/quarkus-extension.yaml is what's used to generate the platform bom. Since the metadata we use for the registry upload is non-enriched, the registry data ends up being incomplete/incorrect.

The quarkus/extensions/schema-registry/confluent/avro extension has a similar mismatch between platform json and the registry, but I can't see a similar 'other directory' mechanism for that one, so the 'other directory' thing might be the wrong tree.

Any idea what's going on, @aloubyansky or @gastaldi?

[gastaldi]

Maybe related to quarkusio/registry.quarkus.io#205?