You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@aloubyansky made a dependency convergence analysis and it appears that some dependencies are not aligned
We could migrate those dependencies, at least using the latests Google Library BOM, but maybe the issue is upsteamd (on Quarkus side) that should use the Google Library BOM.
The text was updated successfully, but these errors were encountered:
I haven't looked into this further, if this is actually a misalignment compared to the quarkus-bom, it probably makes sense to align them going forward. But, just fyi, it's a part of the platform BOM generation process to align version constraints accross all the members. There typically will be adjustments. It depends on what the members bring in though. Which is why we need integration tests in the platform, to make sure the platform BOM works for every member.
I think the best will be to use the Google Library BOM in Quarkus and uses the same version on GCS extensions.
On the library BOM readme, it is say this is the prefered way to manage GRPC / protobuf libraries.
Most of our dependencies are comming from the Quarkus BOM or the Google Library BOM: https://github.com/GoogleCloudPlatform/cloud-opensource-java/wiki/The-Google-Cloud-Platform-Libraries-BOM
@aloubyansky made a dependency convergence analysis and it appears that some dependencies are not aligned
We could migrate those dependencies, at least using the latests Google Library BOM, but maybe the issue is upsteamd (on Quarkus side) that should use the Google Library BOM.
The text was updated successfully, but these errors were encountered: