You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@pekko.apache.org by "darkjh (via GitHub)" <gi...@apache.org> on 2024/08/16 15:37:02 UTC
[D] Migration of big codebase from akka to pekko [pekko]
GitHub user darkjh created 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 contributor to this codebase and this approach will create a lot of conflicts during the testing phase.
I'm wondering has someone tried "smarter" approach? 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 notifications@pekko.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@pekko.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [D] Migration of big codebase from akka to pekko [pekko]
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
GitHub user pjfanning added a comment to the discussion: Migration of big codebase from akka to pekko
Using a shading tool might work but it is complicated. Remember that the config property names have changed too. Some class names that had 'Akka' in the name were changed (to have 'Pekko' in the name instead). Another issue to consider is that not every lib that supports Akka has been converted to support Pekko.
I would still suggest that you consider just using the vanilla approach of changing your code. Many people have gone down this route and we have had few complaints. Text replacement, especially using IDEs, is a pretty painless way to approach the problem. Updating PRs that are in flight is usually pretty easy with modern tooling (to rebase them).
GitHub link: https://github.com/apache/pekko/discussions/1440#discussioncomment-10360640
----
This is an automatically sent email for notifications@pekko.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@pekko.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [D] Migration of big codebase from akka to pekko [pekko]
Posted by "darkjh (via GitHub)" <gi...@apache.org>.
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? 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 notifications@pekko.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@pekko.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [D] Migration of big codebase from akka to pekko [pekko]
Posted by "darkjh (via GitHub)" <gi...@apache.org>.
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 notifications@pekko.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@pekko.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [D] Migration of big codebase from akka to pekko [pekko]
Posted by "raboof (via GitHub)" <gi...@apache.org>.
GitHub user raboof added a comment to the discussion: Migration of big codebase from akka to pekko
Is this a Java project or a Scala project? If it's Scala, I wonder if you could build and share a [scalafix](https://scalacenter.github.io/scalafix/) rule to do the first pass of the migration.
Shading seems hard to get right and leave you with considerable technical depth even if it works...
GitHub link: https://github.com/apache/pekko/discussions/1440#discussioncomment-13098473
----
This is an automatically sent email for notifications@pekko.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@pekko.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org