Split package usage for io.fabric8:openshift-model, io.fabric8:openshift-model-operator

[rsvoboda]

Describe the bug

Quarkus reports split package io.fabric8.openshift.api.model usage in io.fabric8:openshift-model, io.fabric8:openshift-model-operator artifacts.

2021-07-29 13:47:28,761 WARN  [io.qua.arc.dep.SplitPackageProcessor] (build-8) Detected a split package usage 
which is considered a bad practice and should be avoided. Following packages were detected in multiple archives: 
- "io.fabric8.openshift.api.model" found in [io.fabric8:openshift-model, io.fabric8:openshift-model-operator]

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

Build project with quarkus-openshift-client extension and check the console logs.

Output of uname -a or ver

macOS BigSur

Output of java -version

Java 11

GraalVM version (if different from Java)

No response

Quarkus version or git rev

Quarkus 2.1.0.Final

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @geoand

[geoand]

cc @manovotn

[manovotn]

This should be addressed by whoever is the maintainer of the aforementioned packages (any idea who that would be @gsmet or @geoand?).
If not solvable right away, they can whitelist the package as was done in #18743
Alternatively, users will be able to ignore certain packages once #19089 gets incorporated.

[geoand]

We can't really address it now (since it's a k8s client issue).

@manovotn does #19089 allow an extension to provide such configuration?
I don't see a build item which would allow that.

[manovotn]

It doesn't now, we can expand it. Didn't think we would need that as well :-D