Expose sundrio builder-annotations in generated bom

[shawkins]

Is your task related to a problem? Please describe

To finish off quarkusio/quarkus#42991 the generated bom needs to include builder-annotations.

Describe the solution you'd like

To finish off quarkusio/quarkus#42991 the generated bom needs to include builder-annotations.

Describe alternatives you've considered

No response

Additional context

No response

[shawkins]

@manusa can you confirm that quarkus doesn't want to use the bom with deps to at the very least avoid okhttp? Also I see builder-annotations is marked as provided in the pom with deps, which would make it ineligible for import anyway.

[manusa]

Hi @shawkins

Could you please elaborate a little bit more?

Our kubernetes-client-bom-with-deps seems to be outdated at the moment, I can see:

kubernetes-client/pom.xml

Line 1261 in 331ea7f

<include>com.squareup*:*</include>

Which shouldn't be there.

@manusa are you good with just updating the fabric8 pom have builder-annotations not at the provided scope?

I guess we can safely change the scope of our dependency and change our affected poms accordingly since this shouldn't really have impact on the users.

[shawkins]

Could you please elaborate a little bit more?

My end goal is to also expose builder-annotations so that we don't have to independently manage the version in keycloak.

Quarkus is using kubernetes-client-bom (no builder-annotations), not the kubernetes-client-bom-with-deps, to create their bom. But even in the -deps bom builder-annotations is provided.