[BUG] Unable to create ASB subsctiption with azure-messaging-servicebus 7.16.0

[blackr1234]

[BUG] Unable to create ASB subsctiption with azure-messaging-servicebus 7.16.0

[anuchandy]

Hi @blackr1234, thanks for reaching out. The upgrade of spring libraries to the latest azure-core-* and azure-messaging-servicebus for April cadence is yet to happen, this dependency conflict will be resolved once April release of all packages are completed.

At the moment you need to override the core packages at the top of your pom file

<dependencies>
    <dependency>
       <groupId>com.azure</groupId>
       <artifactId>azure-core</artifactId>
       <version>1.48.0</version> 
    </dependency>
    <dependency>
       <groupId>com.azure</groupId>
       <artifactId>azure-xml</artifactId>
       <version>1.0.0</version> 
    </dependency>
    <dependency>
       <groupId>com.azure</groupId>
       <artifactId>azure-core-amqp</artifactId>
       <version>2.9.3</version> 
    </dependency>
    <dependency>
       <groupId>com.azure</groupId>
       <artifactId>azure-messaging-servicebus</artifactId>
       <version>7.16.0</version>
    </dependency>
  …..

[anuchandy]

Hi @blackr1234, glad that the workaround unblocked you. Yes, agree with you, it is a good practice not to pull individual dependencies in the application as it may cause dependency conflicts. If BOM or top-level library aggregating and aligning all dependency versions are available, we should delegate versioning to it. Aligning the dependencies manually was a workaround, which can be removed once all Azure SDK libraries and spring release followed by that, for this April cadence is complete.

[github-actions]

@anuchandy @conniey @lmolkova

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[blackr1234]

Thanks a lot for your help @anuchandy .
I've added those dependencies to override existing versions, now subscription creation is working fine.

I guess the key takeway here is, as a normal SDK user, it isn't a good practice (and it is risky) to manually override the version of individual Azure modules, or I may face compatibililty issues like azure-messaging-servicebus in this case, and instead, I should only be using different versions of spring-cloud-azure-stream-binder-servicebus?