L3 - Default Environment (Required on creation):
Camunda Platform 7.15.7 or later.
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):
- Spin and Connect upstream libraries are compiled against an older Commons version than used in the platform mono repo
- Since Spin and Connect are not tested against Commons 1.10.0, incompatibilities might occur in production
- Build tools like Gradle might be configured to be strict on checking versions in the dependency graph
- When two different dependencies point to different versions of a common dependency, a conflict might be raised => build fails
Steps to reproduce (Required on creation):
In a Spring Boot maven project with Camunda Platform 7.15.7, perform $ mvn dependency:tree -Dverbose | grep "camunda-commons".
Observed Behavior (Required on creation):
You should see the following output:
org.camunda.commons:camunda-commons-utils:jar:1.10.0:compile - version managed from 1.9.0; omitted for duplicate org.camunda.commons:camunda-commons-logging:jar:1.10.0:compile - version managed from 1.9.0; omitted for duplicate
Expected behavior (Required on creation):
No version conflict exists.
Root Cause (Required on prioritization):
Spin and Connect are compiled against Commons 1.9.0 while the modules residing in the platform mono repo are compiled against Commons 1.10.0.
Solution Ideas (Optional):
- Make Spin and Connect use Commons 1.10.0, release them again, bump the Spin and Connect versions in the platform mono repo, release patches of the platform
- Make platform build fail when Commons versions differ
- Consolidate Spin, Connect, and Commons into the Platform mono repo and version it together with the Platform
Hints (optional):
-