bvahdat commented on PR #8266: URL: https://github.com/apache/camel/pull/8266#issuecomment-1235582071
> This looks good to me. The concern I have mainly is about the other runtimes. Especially Karaf. It won't be possible to have all the needed bundles for each non release. So we either remove the features from Karaf or we find a way to support this approach Why would we want to make use of the needed bundles not belonging to the same BOM as that would cause all sorts of problems, no mater if Karaf, Quarkus or SB runtime? If we would continue doing that, then we would run into the same issue as currently on the main branch described in CAMEL-18452 in regards to CAMEL-18451. Let's compare azure-XXX versions in 3.18.1: https://github.com/apache/camel/blob/camel-3.18.1/parent/pom.xml#L86-L96 With the corresponding azure-XXX bundle versions: https://github.com/apache/camel-karaf/blob/main/pom.xml#L130-L140 They are out-of-sync. E.g. `<azure-eventhubs-version>5.11.2</azure-eventhubs-version>` Versus: `<azure-messaging-eventhubs-bundle-version>5.8.0_1</azure-messaging-eventhubs-bundle-version>` But that doesn't need to be that way. If we rely on a given azure-sdk-bom version we can see in one shot what are the corresponding bundles we should come up with: https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.5 Just thinking about a given Apache Camel based integration where camel-azure-eventhubs + camel-azure-servicebus + camel-azure-blobstorage of a given Camel version are all inside the same POM and if their versions are not aligned / consistent then that integration would run into all sorts of problems at runtime with conflicting transitive dependencies. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
