release: quarkus metadatas are not up to date
Bug description
While releasing Camel Quarkus 3.8.0, beanio needed to be excluded in the quarkus-platform bom as the quarkus metadata quarkus-extension.yaml was not up to date. It's not possible to override the metadata in quarkus-platform because it does not even contain the artifactId.
The metadata might not be up to date in main and 3.8.x branch.
Probably because the wrong Maven plugin was declared in the beanio extension:
https://github.com/apache/camel-quarkus/pull/5807
@jamesnetherton would it be more accurate to transfer the ticket ownership to you as you have found the solution ?
@jamesnetherton would it be more accurate to transfer the ticket ownership to you as you have found the solution ?
Yes, I'll take it.