[CAMEL-18452] Integrate azure-sdk-bom in a non-conflicting manner

• Type: Task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.18.1
• Fix Version/s: 3.19.0
• Component/s: camel-azure
• Estimated Complexity: Unknown
• Assignee: Babak Vahdat
• Reporter: Babak Vahdat
• Created: 02/Sep/22 08:56
• Updated: 03/Sep/22 21:56
• Resolved: 03/Sep/22 12:02

Description

While working on CAMEL-18451 I ran into a conflicting Azure dependency issue. To reproduce it just add the following dependency to camel-azure-eventhubs POM without any other additional changes whatsoever:

<dependency>
    <groupId>com.azure</groupId>
    <artifactId>azure-identity</artifactId>
    <version>${azure-identity-version}</version>
</dependency>

and the integration test execution as mentioned here will hang forever until it time outs through the maven-failsafe-plugin.

This is because currently we have the following dependency versions on the main branch:

<azure-eventhubs-version>5.11.2</azure-eventhubs-version>
<azure-identity-version>1.5.1</azure-identity-version>

The currently used azure-eventhubs version belongs to the BOM:

https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.1

Whereas the current azure-identity version belongs to:

https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.2

Each having potentially incompatible / non-matching own transitive dependency versions causing some sort of deadlock behaviour at runtime as explained above.

We better need to make sure that whatever azure-XXX dependencies we have belong to the same azure-sdk-bom version.

I think it's possible to make use of azure-sdk-bom BOM in a non-conflicting manner.

Issue Links

• blocks: CAMEL-18451 camel-azure-eventhubs: Add support for Azure-AD authentication
• relates to: CAMEL-17109 camel-azure dependency bom causes conflicting dependencies to be downloaded
• links to: GitHub Pull Request #8266
• links to: GitHub Pull Request #8268