Task Summary
LICENSE-binary lists two versions of the same library, and both jars actually ship:
org.reactivestreams.reactive-streams-1.0.3.jar
org.reactivestreams.reactive-streams-1.0.4.jar
Goal: stop shipping reactive-streams 1.0.3 so the binary distribution carries only one copy and LICENSE-binary can drop the duplicate entry.
Where each version ships
| Subproject |
Version on runtime classpath |
amber, computing-unit-managing-service, file-service, workflow-compiling-service |
1.0.4 |
access-control-service, config-service |
1.0.3 |
Root cause
reactive-streams is purely transitive — no build.sbt declares it directly. The 1.0.3 chain in the two affected services is:
access-control-service / config-service
└─ org.jooq:jooq:3.16.23 (direct dep in common/dao)
└─ io.r2dbc:r2dbc-spi:0.9.0.RELEASE
└─ org.reactivestreams:reactive-streams:1.0.3
Priority
P2 – High
Task Type
By submitting this issue, you agree to follow the Apache Code of Conduct.
Task Summary
LICENSE-binarylists two versions of the same library, and both jars actually ship:Goal: stop shipping
reactive-streams 1.0.3so the binary distribution carries only one copy andLICENSE-binarycan drop the duplicate entry.Where each version ships
amber,computing-unit-managing-service,file-service,workflow-compiling-service1.0.4access-control-service,config-service1.0.3Root cause
reactive-streamsis purely transitive — nobuild.sbtdeclares it directly. The1.0.3chain in the two affected services is:Priority
P2 – High
Task Type
By submitting this issue, you agree to follow the Apache Code of Conduct.