Fabric8 - many (130+) dependencies in generated BOM

[rsvoboda]

Description

Our generated BOM contains a many (130+) io.fabric8-related dependencies in the BOM.

While Guillaume did some work to reduce the cost of this in the Maven resolve, there's still a cost associated to it. I'm wondering if we should be a bit more careful about it.

There are several areas of fabri8 artifacts that might not be needed, e.g. artifact ending with -examples or -tests, some models and integrations (e.g. volcano doesn't seem to be used in quarkus / quarkiverse)

Note that the answer might very well be yes we need to keep all of them but I wanted to make sure we are aware of the situation.

See generated BOM here: https://central.sonatype.com/artifact/io.quarkus/quarkus-bom .

And search for <groupId>io.fabric8</groupId>, there are 131 hits atm.

Whole kubernetes-client-bom is imported in https://github.com/quarkusio/quarkus/blob/main/bom/application/pom.xml#L375 now

            <!-- Kubernetes-client dependencies, imported as a BOM -->
            <dependency>
                <groupId>io.fabric8</groupId>
                <artifactId>kubernetes-client-bom</artifactId>
                <version>${kubernetes-client.version}</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>

This is inspired by #44771 issue created by @gsmet

Implementation ideas

No response

[quarkus-bot]

/cc @geoand (kubernetes), @iocanel (kubernetes)

[geoand]

cc @manusa @metacosm

[manusa]

I created the following issues to deal with the problem upstream:

• [config] Don't publish test and example modules to Maven Central fabric8io/kubernetes-client#6675
• [config] Exclude test and example modules from the BOM modules fabric8io/kubernetes-client#6676

Additional polishing and wiring can also be done at the Quarkus level.