GitHub user raboof edited a discussion: Should we allow 'mixed versioning'?
Currently, Pekko does not allow 'mixed versioning' - please read https://pekko.apache.org/docs/pekko/current/common/binary-compatibility-rules.html#mixed-versioning-is-not-allowed to get the background. This is causing confusion: people see the `IllegalStateException` and assume there is something wrong with Pekko, not with their project. We could consider dropping the requirement to have aligned versions. This means we can no longer make changes to, say, `pekko-stream` that also require changes to `pekko-actor` (even when remaining binary compatible in the user-facing API). Personally, I think requiring aligned versions for artifacts that are released together (e.g. between `pekko-actor` and `pekko-stream`, but not between `pekko-actor` and `pekko-connector-mqtt`) is reasonable, and allowing mixed versioning would restrict changes too much. We should probably make the behavior less confusing, though. Perhaps instead of logging an `IllegalStateException`, we should explain the problem in an `ERROR`-level log message and shut down? GitHub link: https://github.com/apache/pekko/discussions/1483 ---- This is an automatically sent email for notifications@pekko.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@pekko.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
