Use Quarkus Platform BOMs #20570
Comments
ghost
added
the
|
@ASzc Is this ok for productization? |
|
I think we'll need to be kept in the loop so the product build parameters can be updated when needed. However, this shouldn't cause problems |
|
Marginal preference for io.quarkus.platform BOMs. I'm not sure if this universe bom appears in RHBQ |
|
Based on discussion with Quarkus team, we should be using the combination of |
|
WIP branch (with lots of failed tests :)): https://github.com/vmuzikar/keycloak/tree/platform-bom |
Pepo48
added a commit
to Pepo48/keycloak
that referenced
this issue
Jul 2, 2023
* added Quarkus Platform BOM * added Quarkus Operator SDK BOM Closes keycloak#20570 Signed-off-by: Peter Zaoral <[email protected]>
vmuzikar
pushed a commit
to vmuzikar/keycloak
that referenced
this issue
Jul 4, 2023
Closes keycloak#20570 Closes keycloak#15870 Co-authored-by: Peter Zaoral <[email protected]>
abstractj
pushed a commit
that referenced
this issue
Jul 6, 2023
Closes #20570 Closes #15870 Co-authored-by: Peter Zaoral <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
To further align with Quarkus, we should be using the Platform BOMs. In particular:
io.quarkus.platform:quarkus-bomio.quarkus.platform:quarkus-operator-sdk-bom. This in particular is important as we won't be no longer specifying an Operator SDK version but rather using the version that comes with a certain Quarkus version.An alternative is to use a single BOMio.quarkus:quarkus-universe-bom.This also includes cleaning up the dependency overrides we no longer need.
The text was updated successfully, but these errors were encountered: