Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Upgrading to Play 3.0 #4

Open
rtyley opened this issue Feb 21, 2024 · 0 comments
Open

Upgrading to Play 3.0 #4

rtyley opened this issue Feb 21, 2024 · 0 comments

Comments

@rtyley
Copy link
Member

rtyley commented Feb 21, 2024 •
edited

Base assumption: Project is already on Play 2.8 or above

  • A key benefit of Play 3.0 over previous versions of Play is the Akka → Pekko #5 transition, removing the Akka BSL licensing concerns.
  • All the steps in Upgrading to Play 2.9 #1 will need to be completed first, though you may be able to skip straight from Play 2.8 to 3.0. You might want to go via Play 2.9 if the project upgrade is large and you want to break the upgrade process down into smaller chunks, saving the Akka→Pekko transition till last.

Examples
This was referenced Feb 21, 2024
Open
Open
rtyley added a commit to guardian/facia-scala-client that referenced this issue Feb 28, 2024
@rtyley
Add Play v2.9 support to aid Facia Tool upgrade
34c196b 
Whether you get benefit from going 2.8->2.9->3.0 (over just going 2.8->3.0) is probably a factor
of how big and complicated the project being upgraded is - I'd guess Facia Tool is quite big, so
breaking the changes down into smaller chunks might be worth it in terms of avoiding risk.

Note also that Play 2.9 actually uses Play-Json *2.10*, which is a bit surprising!

See also guardian/maintaining-scala-projects#4
@rtyley rtyley mentioned this issue Feb 28, 2024
Merged
@rtyley rtyley mentioned this issue Mar 12, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rtyley