GitHub user mdedetrich added a comment to the discussion: Strategy for gradual Akka → Pekko migration with shared library and rollback capability?
> I'm more concerned about conflicting transitive dependencies. The Pekko 1.0.x series is strictly a fork of Akka 2.6 without any changes to dependencies, only package names/conf paths and any related changes are done. This was a deliberate decision to make migration smoother. If you are talking about transitive dependencies further down the chain (i.e. you have library that depends on Akka 2.6 but it isn't compiled against Pekko 1.0.x that isn't a satellite Pekko project) then you have to have to either fork it and make a version built against Pekko 1.0.x or if its an internal library then cross build it, scala-rewrite-imports should help here as well along with the use of sbt subprojects. GitHub link: https://github.com/apache/pekko/discussions/2592#discussioncomment-15286941 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
