Import grpc-bom in quarkus-bom instead of managing individual grpc artifacts #9403
Labels
area/housekeeping
Issue type for generalized tasks not related to bugs or enhancements
Milestone
Description
Since the GRPC extension was moved to Quarkus source tree, we (Camel Quarkus) have hard time to align dependencies coming from Quarkus with the one coming from Camel. This is because Quarkus runtime BOM manages just
grpc-api
andgrpc-stub
. We'd actually need much more, nearly all listed in https://repo1.maven.org/maven2/io/grpc/grpc-bom/1.29.0/grpc-bom-1.29.0.pomSo is there a reason not to import the whole grpc-bom in quarkus-bom?
The text was updated successfully, but these errors were encountered: