You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 21, 2023. It is now read-only.
It'd be good to stop depending on Interplay. Maintaining scala cross versions, having to move upstream (from play-foo to interplay) for each imrpovement, etc... is becoming more of a blocker than a benefit.
Each downstream project should inherit whichever pieces of interplay it deems necessary and maintain them separately. Here's a list of projects using interplay:
@mkurz I finished the work on this. Can you review? 😉
Or just we can merge these PR's without review and I will fix problems in the future if something is wrong at release.
It'd be good to stop depending on Interplay. Maintaining scala cross versions, having to move upstream (from play-foo to interplay) for each imrpovement, etc... is becoming more of a blocker than a benefit.
Each downstream project should inherit whichever pieces of interplay it deems necessary and maintain them separately. Here's a list of projects using interplay:
Copy interplay into main repository playframework#11987
Drop interplay omnidoc#268
Drop interplay play-doc#206
Drop interplay scalatestplus-play#447
Drop interplay play-socket.io#214
Drop interplay play-slick#773
Drop interplay anorm#587
No longer use
interplay
:play-json--> already uses its own copy ofOmnidoc.scala
twirl--> already uses its own copy ofOmnidoc.scala
play-soapEOL projects that refer to
interplay
(false positives):play-native-loader--> archived EOLplay-spring-loader--> archived EOLplay-enhancer--> archived EOLplay-iteratees--> archived EOLThe text was updated successfully, but these errors were encountered: