Akka already has checks to make sure users don't mix and match different artifacts on the class path. There is undergoing work in Pekko to remove/fix these checks (i.e. see https://github.com/apache/incubator-pekko/pull/189) however it does bring a general point about whether we should check if there are any Akka artifacts on the classpath for users running Pekko and produce warnings in such a case.
I would predict that generally speaking if you are mixing Pekko and Akka artifacts then this is likely a mistake and you are doing something wrong even though technically speaking with all of the class/package/conf changes there shouldn't be any conflicts (basically both ecosystems would sit in their own silos). Thoughts? -- Matthew de Detrich *Aiven Deutschland GmbH* Immanuelkirchstraße 26, 10405 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen *m:* +491603708037 *w:* aiven.io *e:* [email protected]
