GitHub user pjfanning added a comment to the discussion: Should we allow 'mixed versioning'?
We have a config to disable the check. `pekko.fail-mixed-versions=off` I think Akka and existing Pekko users are used to check so I would prefer to keep some form of check - especially since it can be turned off. We have BOMs like [pekko-bom](https://mvnrepository.com/artifact/org.apache.pekko/pekko-bom) but these might not be supported by sbt (but help with Maven and Gradle). I am not against changing away from the way the issue is reported and think that Arnout's suggestion repeated below is worth considering. ``` 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 ``` We could also consider only comparing the major and minor parts the x.y.z version number but allow flexibility with the patch part of the version number ('z' in x.y.z). GitHub link: https://github.com/apache/pekko/discussions/1483#discussioncomment-10668587 ---- 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
