Conversation
operator/pom.xml
Outdated
There was a problem hiding this comment.
@mabartos you're right, we should not need it anymore. Addressed.
Thanks.
There was a problem hiding this comment.
@mabartos I actually found out that OLM CI workflow is failing due to this change (see the comparison between this and this). So far I haven't found the connection between the property existence and the operator deployment, but I haven't investigated it properly just yet.
Does it ring any bell right away? I plan to test it on a local cluster tomorrow.
There was a problem hiding this comment.
It does ring a bell. We're overriding the version in the root POM to something that's incompatible with Quarkus. We should remove all the overrides we don't need, see my comment below.
There was a problem hiding this comment.
I resolved it for now. The question is though, what should we do in case that the provided version from the platform BOM is currently older than the one we currently use in the project?
Speaking about WF common, the difference is 1.6.0 compared to 1.5.4 (provided by the BOM). As it can be seen in my latest commit, I approached it by removing the dependency override from the parent POM and then I overrode the dependency version on the submodule level.
Is this the desired approach?
There was a problem hiding this comment.
@Pepo48 Works for me but we'll need a blessing from the core team at minimum once this PR is finalized.
40ac490 to
56db0de
Compare
ASzc
left a comment
There was a problem hiding this comment.
Seems ok from a product perspective. The runtime/buildtime version property split has been kept, so that's good
There was a problem hiding this comment.
@Pepo48 Thanks for the PR.
Part of the effort around using Quarkus BOM is to stop specifying versions of the dependencies that are already present in the BOM. I think there are lots of them in the root POM. Do you plan to address it in this PR, or will it be a follow-up? Either way works for me. We need to be careful now about not doing anything too dangerous now, just days before release.
I am working on it in a separate testing branch just for now, the intersection is quite big (at least based on my analysis from two days ago it's not just couple of dependencies). I'm testing it continuously, I didn't want to clutter this PR with unnecessary force pushes in order to re-run the CI every single time. And yes, my original intention was to keep it separate just because of the size. But I can easily merge it, it doesn't matter to me much. I will finish the rest of the cleanup tomorrow. |
What was removed from the parent BOM:What can be pottentially removed (and for now I left untouched):
Things I would like to discuss before I address them:
Edit: I'm already aware about the test failures. |
9a1accc to
7f4852f
Compare
ghost
left a comment
There was a problem hiding this comment.
Unreported flaky test detected, please review
Unreported flaky test detectedIf the below flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.model.session.SessionTimeoutsTest#testOfflineUserClientMaxLifespanSmallerThanSessionKeycloak CI - Store Model Tests |
* added Quarkus Platform BOM * added Quarkus Operator SDK BOM Closes keycloak#20570 Signed-off-by: Peter Zaoral <[email protected]>
* removed WildFly dependencies from the Quarkus module Signed-off-by: Peter Zaoral <[email protected]>
* overridden dependencies cleanup Signed-off-by: Peter Zaoral <[email protected]>
* reverted some changes in order to stabilize the testsuite * upgraded quarkus Signed-off-by: Peter Zaoral <[email protected]>
* reverted Quarkus upgrade as it is going to be handled separately in keycloak#21352 Signed-off-by: Peter Zaoral <[email protected]>
|
jFTR, #21352 will (most likely*) affect the dependency list above in a following way: *I compared it with 3.2.0.CR1, because the final platform BOMs were not released just yet. |
|
This is currently waiting for Quarkus Platform BOMs 3.2.0.Final to be released. |
Closes #20570
Closes #15870
Signed-off-by: Peter Zaoral [email protected]
I might've missed dependencies that can be removed as a part of this PR. Therefore, please, let me know if you find such during the review. Thanks!