Closed hzpz closed 1 week ago
A workaround is to pin grpc-java to version 1.65.1:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>io.grpc</groupId>
<artifactId>grpc-bom</artifactId>
<version>1.65.1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
This library does not manage dependency versions for you. Thank you for posting the resolution.
Thanks for your reply!
I would argue that managing dependencies is exactly what a Spring Boot starter does. Besides a few other things like contributing auto-configurations.
In any case, it is very inconvenient for users to have two libraries of the same project with the same version number having incompatible transitive dependencies. I would very much appreciate it if you would reconsider your answer.
In fact, spring-boot manages the dependencies in a bom: https://github.com/spring-projects/spring-boot/blob/v3.3.3/spring-boot-project/spring-boot-dependencies/build.gradle
Internally, spring-zeebe has a managed grpc version: https://github.com/camunda-community-hub/spring-zeebe/blob/main/pom.xml#L84-L90
The mismatch comes from the fact that the test library we build on lives outside the camunda monorepo. However, this will change in October with the release of a new test library.
As this library will also be deprecated and replaced with the official camunda sdk, I would not like to introduce a dedicated bom now.
Describe the bug
When using
spring-boot-starter-camunda
andspring-boot-starter-camunda-test
version 8.5.10,@ZeebeSpringTest
s will fail with aClassNotFoundException
.It seems that
spring-boot-starter-camunda-test
depends on version 1.62.2 of grpc-java, whilespring-boot-starter-camunda
expects version 1.65.1 to be on the classpath.To Reproduce
spring-boot-starter-camunda
andspring-boot-starter-camunda-test
dependenciesDemoApplicationTests
mit@ZeebeSpringTest
Expected behavior
The test should pass.
Log/Stacktrace
Environment: