You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Babak Vahdat (Jira)" <ji...@apache.org> on 2022/09/03 12:03:00 UTC
[jira] [Resolved] (CAMEL-18452) Integrate azure-sdk-bom in a non-conflicting manner
[ https://issues.apache.org/jira/browse/CAMEL-18452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Babak Vahdat resolved CAMEL-18452.
----------------------------------
Resolution: Fixed
> Integrate azure-sdk-bom in a non-conflicting manner
> ---------------------------------------------------
>
> Key: CAMEL-18452
> URL: https://issues.apache.org/jira/browse/CAMEL-18452
> Project: Camel
> Issue Type: Task
> Components: camel-azure
> Affects Versions: 3.18.1
> Reporter: Babak Vahdat
> Assignee: Babak Vahdat
> Priority: Minor
> Fix For: 3.18.2, 3.19.0
>
>
> 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:
> {code:java}
> <dependency>
> <groupId>com.azure</groupId>
> <artifactId>azure-identity</artifactId>
> <version>${azure-identity-version}</version>
> </dependency>
> {code}
> and the integration test execution as mentioned [here|https://camel.apache.org/components/3.18.x/azure-eventhubs-component.html#_development_notes_important] 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:
> {code:java}
> <azure-eventhubs-version>5.11.2</azure-eventhubs-version>
> <azure-identity-version>1.5.1</azure-identity-version>
> {code}
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)