search

apache / pekko-persistence-r2dbc

Asynchronously writes journal and snapshot entries to configured R2DBC databases so that Apache Pekko Actors can recover state
https://pekko.apache.org/
Apache License 2.0
14 stars 6 forks source link

investigate pekko dependency issues in nightly tests (1.0) #128

Open pjfanning opened 3 months ago

pjfanning commented 3 months ago

https://github.com/apache/pekko-persistence-r2dbc/actions/runs/9575949941

[info] R2dbcOffsetStoreSpec:
[info] org.apache.pekko.projection.r2dbc.R2dbcOffsetStoreSpec *** ABORTED *** (23 milliseconds)
[info]   java.lang.IllegalStateException: You are using version 1.0.1 of Apache Pekko, but it appears you (perhaps indirectly) also depend on older versions of related artifacts. You can solve this by adding an explicit dependency on version 1.0.1 of the [pekko-stream-typed, pekko-persistence-typed, pekko-serialization-jackson, pekko-remote, pekko-pki] artifacts to your project. Here's a complete collection of detected artifacts: (1.0.0+26-fbac70e9-SNAPSHOT, [pekko-persistence-typed, pekko-pki, pekko-remote, pekko-serialization-jackson, pekko-stream-typed]), (1.0.1, [pekko-actor, pekko-actor-testkit-typed, pekko-actor-typed, pekko-persistence, pekko-persistence-query, pekko-protobuf-v3, pekko-slf4j, pekko-stream, pekko-stream-testkit, pekko-testkit]). See also: https://pekko.apache.org/docs/pekko/current/common/binary-compatibility-rules.html#mixed-versioning-is-not-allowed
[info]   at org.apache.pekko.util.ManifestInfo.checkSameVersion(ManifestInfo.scala:188)
Roiocam commented 3 months ago

@pjfanning

Because the core dependency has been updated to 1.0.1, but other dependencies still rely on pekko-core 1.0.0

https://github.com/apache/pekko-persistence-r2dbc/blob/a8ea6e6fc2ab4a704bcfc8e36b18e56f3b45a835/project/Dependencies.scala#L20-L25