Open adpi2 opened 1 year ago
@mfirry Yes indeed and I don't think we have a license for it. So maybe we should replace it with Pekko.
I deleted the comment, but thanks @adpi2 for your reply. I'll think about this.
Actually we should have a license for Akka soon. I'll keep you updated about it.
Thanks @adpi2. I did give it a try to "just" work on core (and the easy way for me was to sort of split it up on its own repo). With the precious help from @TonioGela, we made it compile. Please have a look in your own good time https://github.com/mfirry/scaladex-core
As far as I can see all other modules need Akka.
Thanks @adpi2. I did give it a try to "just" work on core (and the easy way for me was to sort of split it up on its own repo). With the precious help from @TonioGela, we made it compile
Yay, that looks beautiful!
So I can confirm that we have a license for Akka but it is a temporary one. I would rather try to migrate to Pekko than to renew our Akka license every year.
Ok. How do you suggest one can go ahead? What order would you suggest projects should be worked? I see these: infra, webclient, server, core, data? Am I missing anything?
Ok. How do you suggest one can go ahead? What order would you suggest projects should be worked? I see these: infra, webclient, server, core, data? Am I missing anything?
Here is the migration to Pekko: https://github.com/scalacenter/scaladex/pull/1338
Before starting the migration I would check that every library is Scala 3 compatible, and update them if needed. For the one that are not Scala 3 compatible I would configure them with CrossVersion.for3Use2_13
.
Then I would suggest this order of projects: core, webclient, infra, data, server.
Here is the migration to Pekko: https://github.com/scalacenter/scaladex/pull/1338
It's merged
Sorry... got lost in so many things. Has anyone moved in any direction here? If not, I'll try and make a proper step-by-step upgrade during the summer. Let me know @adpi2 and thanks.
Hi @mfirry I am working on this and also documenting the steps :)
Ah cool. Anything public I can see and follow?
Ah cool. Anything public I can see and follow?
not yet, will share soon :)
Hi @kannupriyakalra ... any update?
Motivation
Compile with Scala 3
Identified Obstacles
CrossVersion.for3Use2_13
.CrossVersion.for3Use2_13
.Implementation Guideline
core
moduleCrossVersion.for3Use2_13
for libraries that are not yet compatible with Scala 3.CrossVersion.for3Use2_13
does not work it can be because of conflicting transitive dependencies, or it could be that we need to use Macros. Can we resolve those conflicting dependencies manually? Can we stop using the macros?infra
orclient
until every module compiles to Scala 3.Expectations