GitHub user darkjh edited a discussion: Migration of big codebase from akka to pekko
Hello, I'm planning to migrate a big java codebase from akka 2.6.21 to pekko 1.0.0. To give an idea, there's over ~1800 files containing akka symbol import. The obvious option is to rename every import from `akka.*` to `org.apache.pekko.*` and adapt any config overrides in the codebase. However there's many active contributors to this codebase and this approach will create a lot of conflicts during the testing phase. I'm wondering has someone tried "smarter" approach to avoid the import changes? I tried using maven shade plugin to relocate classes from `org.apache.pekko` to `akka` and adapts some config values, and this seems to work for small examples. Maybe we can also intercept class loading and proxy the akka classes to pekko ones? Has anyone tried these "smarter" ways and are they worth pursuing? Thanks! GitHub link: https://github.com/apache/pekko/discussions/1440 ---- 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]
