You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pekko.apache.org by GitBox <gi...@apache.org> on 2022/11/05 22:13:43 UTC
[GitHub] [incubator-pekko] danischroeter opened a new issue, #22: Provide an automated migration to migrate from akka to pekko
danischroeter opened a new issue, #22:
URL: https://github.com/apache/incubator-pekko/issues/22
We should provide some automated migration that users of akka can use that adapts their codebase to use pekko.
This migration should automatically
* adapt the dependencies
* in sbt
* in maven
* adapt the codebase
* imports in scala
* imports in java
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
[GitHub] [incubator-pekko] jrudolph commented on issue #22: Provide an automated migration to migrate from akka to pekko
Posted by "jrudolph (via GitHub)" <gi...@apache.org>.
jrudolph commented on issue #22:
URL: https://github.com/apache/incubator-pekko/issues/22#issuecomment-1457916391
I'm setting up a simple scalafix rule to at least take care of the imports in Scala files (though that's also easy to change using search/replace).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
[GitHub] [incubator-pekko] pjfanning commented on issue #22: Provide an automated migration to migrate from akka to pekko
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #22:
URL: https://github.com/apache/incubator-pekko/issues/22#issuecomment-1566251245
Thanks @jtjeferreira
We're running into real issues with getting a release done. A lot of them are arguments about process and others are about copyrights and stuff like that.
For me, it's better if people release their own code. As soon as we take it on, we have to jump through loads of non-code hoops.
I had a quick look at the code you have. I'm not a Scalafix expert but I'm not sure if your changes cover some pretty common renaming issues. You cover the package name fixing but there are class names with Akka in them and we replace those with Pekko.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
[GitHub] [incubator-pekko] gmethvin commented on issue #22: Provide an automated migration to migrate from akka to pekko
Posted by GitBox <gi...@apache.org>.
gmethvin commented on issue #22:
URL: https://github.com/apache/incubator-pekko/issues/22#issuecomment-1305471337
I think the first step here is understanding all the things that would need to change in someone's app, so we can develop a strategy for each.
The first obvious step is to change the akka-* dependencies to pekko-* dependencies, and replace the package name in the codebase. But I'd imagine most production applications running Akka have at least one third-party dependency that's not an official Akka library, so we also need to migrate those to the equivalent compatible version. Maybe the best solution there is to allow the user to provide a mapping of dependencies (groupId, artifactId, version) to their pekko equivalents, and we can provide a suggested mapping for common libraries.
Another tricky thing is how to handle configuration. I think it's too risky to just provide a tool to migrate the configuration file itself, since configuration can come from many different sources in a real production app. We'd probably want a way to tell pekko to look at both pekko and akka prefixes, or a list of arbitrary user-specified config prefixes.
Then there's the question of how to migrate akka remote/artery applications away from `akka://`. This is another situation where we probably want to make it configurable in Pekko, so the user initially wouldn't have to do anything.
Ultimately I imagine what we'd want to have is a migration guide, with some automated tools to handle parts of the migration.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
[GitHub] [incubator-pekko] pjfanning commented on issue #22: Provide an automated migration to migrate from akka to pekko
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #22:
URL: https://github.com/apache/incubator-pekko/issues/22#issuecomment-1566252475
https://pekko.apache.org/docs/pekko/current//project/migration-guides.html covers Pekko core. @jtjeferreira Your changes look a useful tool - and it's good that you've also supported Alpakka migration.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
[GitHub] [incubator-pekko] spangaer commented on issue #22: Provide an automated migration to migrate from akka to pekko
Posted by GitBox <gi...@apache.org>.
spangaer commented on issue #22:
URL: https://github.com/apache/incubator-pekko/issues/22#issuecomment-1355093498
I guess, documenting trial and error hand conversions with 'early builds' would be meaningful input?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
[GitHub] [incubator-pekko] sam-byng commented on issue #22: Provide an automated migration to migrate from akka to pekko
Posted by "sam-byng (via GitHub)" <gi...@apache.org>.
sam-byng commented on issue #22:
URL: https://github.com/apache/incubator-pekko/issues/22#issuecomment-1507218776
Does this need to go into Pekko 1.0.0 milestone?
It seems to me that this is a 'would be nice if' item that could go into the pekko 1.1.0 milestone.
I found migration using the [migration guide](https://github.com/apache/incubator-pekko/blob/main/docs/src/main/paradox/project/migration-guides.md) was quite a lightweight initial solution.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
[GitHub] [incubator-pekko] sam-byng commented on issue #22: Provide an automated migration to migrate from akka to pekko
Posted by "sam-byng (via GitHub)" <gi...@apache.org>.
sam-byng commented on issue #22:
URL: https://github.com/apache/incubator-pekko/issues/22#issuecomment-1511070916
Ok I think that sounds fine. Could we label as 'nice to have (low prio)' so that people can see that?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
[GitHub] [incubator-pekko] pjfanning commented on issue #22: Provide an automated migration to migrate from akka to pekko
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #22:
URL: https://github.com/apache/incubator-pekko/issues/22#issuecomment-1507272494
This is not a release blocker. We can live without it but can we leave it open in case someone wants to try to do something with it?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
Re: [I] Provide an automated migration to migrate from akka to pekko [incubator-pekko]
Posted by "mkurz (via GitHub)" <gi...@apache.org>.
mkurz commented on issue #22:
URL: https://github.com/apache/incubator-pekko/issues/22#issuecomment-1774998072
scala-steward can also run scalafix migration rules (https://github.com/scala-steward-org/scala-steward/blob/main/docs/scalafix-migrations.md) when opening pull requests.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
[GitHub] [incubator-pekko] jtjeferreira commented on issue #22: Provide an automated migration to migrate from akka to pekko
Posted by "jtjeferreira (via GitHub)" <gi...@apache.org>.
jtjeferreira commented on issue #22:
URL: https://github.com/apache/incubator-pekko/issues/22#issuecomment-1566249253
Hi! I wrote an scalafix migration rule in https://github.com/jtjeferreira/pekko-scalafix which I unit tested in a small [sample](https://github.com/jtjeferreira/pekko-scalafix/blob/main/input/src/main/scala/fix/PekkoScalafix.scala), but also which I tested locally against an [akka-sample project](https://github.com/akka/akka-samples/tree/main/akka-sample-sharding-scala)
Would you accept a PR of this code? Or should I publish it myself?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
[GitHub] [incubator-pekko] jtjeferreira commented on issue #22: Provide an automated migration to migrate from akka to pekko
Posted by "jtjeferreira (via GitHub)" <gi...@apache.org>.
jtjeferreira commented on issue #22:
URL: https://github.com/apache/incubator-pekko/issues/22#issuecomment-1569135709
> You cover the package name fixing but there are class names with Akka in them and we replace those with Pekko.
Thanks, I fixed those
> Is there anything that can be done to migrate configs?
I am not s scalafix expert either, but I don't think so...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
[GitHub] [incubator-pekko] an-tex commented on issue #22: Provide an automated migration to migrate from akka to pekko
Posted by GitBox <gi...@apache.org>.
an-tex commented on issue #22:
URL: https://github.com/apache/incubator-pekko/issues/22#issuecomment-1305824583
Another tricky area will be migration of akka persistence. Especially around the serializers as they might leak some akka references too.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
[GitHub] [incubator-pekko] He-Pin commented on issue #22: Provide an automated migration to migrate from akka to pekko
Posted by "He-Pin (via GitHub)" <gi...@apache.org>.
He-Pin commented on issue #22:
URL: https://github.com/apache/incubator-pekko/issues/22#issuecomment-1511083121
I will add that soon
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org
[GitHub] [incubator-pekko] pjfanning commented on issue #22: Provide an automated migration to migrate from akka to pekko
Posted by "pjfanning (via GitHub)" <gi...@apache.org>.
pjfanning commented on issue #22:
URL: https://github.com/apache/incubator-pekko/issues/22#issuecomment-1561253918
Useful but not going to be a blocker for '1.0.0' release
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org