Play Framework
Replies: 6 comments 20 replies
-
|
Did you try |
Beta Was this translation helpful? Give feedback.
-
|
I tried out the The following works: crossScalaVersions := Seq("2.13.12", "3.3.1")
scalaVersion := crossScalaVersions.value.headThis does not: scalaVersion := "3.3.1"Please note, the sbt compilation and running the project always worked. The problem I'm having is simply that IntelliJ shows errors. Is this an issue with IntelliJ not properly supporting Scala 3 projects? |
Beta Was this translation helpful? Give feedback.
-
|
Here are some more troubles I had to address, just so they are documented somewhere, maybe it helps someone (or myself) in the future. After opening my play 3.0 / scala 3 / sbt 1.9.7 / jdk 21 project in IntelliJ, I have to manually do the following:
|
Beta Was this translation helpful? Give feedback.
-
|
@hertg Seems you are not alone: https://discord.com/channels/931647755942776882/931955815479402546/1174312904397434951 |
Beta Was this translation helpful? Give feedback.
-
|
For the record - IntelliJ ticket here: https://youtrack.jetbrains.com/issue/SCL-21800/Highlightning-of-Pekko-classes-works-for-Scala-2.13.12-but-not-for-Scala-3.3.1 |
Beta Was this translation helpful? Give feedback.
-
|
Update I've upgraded my project to Scala 3 today and found that this issue has been resolved. However, there is another issue where in my play-java project most Java source files had syntax highlighting disabled. I found the following bug report at IntelliJ: In order to fix this issue, one can disable the |
Beta Was this translation helpful? Give feedback.
-
|
@mkurz Hi Matthias, quick question, are there issues to be expected in moving to a Scala 3 project (no cross-version), or should this work in your opinion? I see that in the sample projects, you are still using cross-versioning with Scala 2.13. Is there any reason for that? I tried to go full Scala 3, and it seemed to work quite well, but sometimes I get random |
Beta Was this translation helpful? Give feedback.
-
|
Oh, that clears up some things for me, thanks for pointing it out. Yeah, I've used cross-compilation before, for libraries that had to be cross-compiled between 2.12 and 2.13. The cross-compilation in the sample projects threw me off a bit (especially with 2.13 / 3, because I'm less familiar with their compatability) so I assumed that there is a need for that in non-library projects when using differing libraries. I'm inclined to blame it on IntelliJ now, it seems that after I started it in the sbt shell, it now works with the Play App run configuration too... Weird. I'll make sure to note it somewhere if I figure out more about it. Thanks for your responses, even though Play clearly isn't at fault here, appreciate your help. |
Beta Was this translation helpful? Give feedback.
-
|
You are welcome 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Is there a reason to wait on updating sbt to sidenote: the sbt shell also caused the NoClassDefFound error, I haven't seen it yet when running manually from the terminal. I also just updated my Scala plugin from |
Beta Was this translation helpful? Give feedback.
-
No, absolutely no reason to wait. You can use 1.10 right now. |
Beta Was this translation helpful? Give feedback.
-
|
Update: It seems like it's working now, but every time I start the project, I get tons of Scala compiler errors on the first request. All of them seem to be related to imports in my twirl templates. Upon initiating a second request, it starts compiling again, and then everything works fine 🤔 Play heavily truncated and redacted [info] compiling 143 Scala sources and 1 Java source to /mnt/data/repositories/myproject/target/scala-3.3.3/classes ...
[error] /mnt/data/repositories/myproject/app/org/example/myproject/account/views/webauthn_rename.scala.html:1:1: value utils is not a member of org.example.myproject.template
[error] @import org.example.myproject.account.models.FormFidoName
[error] ^
[error] /mnt/data/repositories/myproject/app/org/example/myproject/account/views/setup_webauthn_success.scala.html:1:1: value utils is not a member of org.example.myproject.template
[error] @import org.example.myproject.account.models.FormFidoName
[error] ^
[error] /mnt/data/repositories/myproject/app/org/example/myproject/account/views/setup_webauthn_start.scala.html:1:1: value utils is not a member of org.example.myproject.template
[error] @import org.example.myproject.account.views.html.account_layout
[error] ^
...
An unhandled exception was thrown in the compiler.
Please file a crash report here:
https://github.com/lampepfl/dotty/issues/new/choose
while compiling: <no file>
during phase: parser
mode: Mode()
library version: version 2.13.12
compiler version: version 3.3.3
...
[error] ## Exception when compiling 679 sources to /mnt/data/repositories/myproject/target/scala-3.3.3/classes
[error] java.lang.StackOverflowError
[error] dotty.tools.dotc.typer.Typer.typed(Typer.scala:3191)
[error] dotty.tools.dotc.typer.Typer.typedExpr(Typer.scala:3303)
[error] dotty.tools.dotc.typer.Namer.typedAheadExpr$$anonfun$1(Namer.scala:1656)
[error] dotty.tools.dotc.typer.Namer.typedAhead(Namer.scala:1646)
[error] dotty.tools.dotc.typer.Namer.typedAheadExpr(Namer.scala:1656)
[error] dotty.tools.dotc.typer.Namer$Completer.$anonfun$15(Namer.scala:794)
...
[error] (Compile / compileIncremental) java.lang.StackOverflowError
ERROR o.a.p.a.ActorSystemImpl - Internal server error, sending 500 response
scala.MatchError: java.lang.StackOverflowError (of class java.lang.StackOverflowError)
at play.sbt.run.PlayReload$.$anonfun$taskFailureHandler$8(PlayReload.scala:92)
at scala.Option.map(Option.scala:230)
at play.sbt.run.PlayReload$.taskFailureHandler(PlayReload.scala:92)
at play.sbt.run.PlayReload$.$anonfun$compile$3(PlayReload.scala:144)
at scala.util.Either$LeftProjection.map(Either.scala:573)
at play.sbt.run.PlayReload$.compile(PlayReload.scala:144)
at sbt.PlayRun$.$anonfun$playRunTask$5(PlayRun.scala:99)
at play.runsupport.Reloader.$anonfun$reload$1(Reloader.scala:495)
at play.runsupport.Reloader$$anon$1.run(Reloader.scala:58)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:400) |
Beta Was this translation helpful? Give feedback.
-
Are you using annotations somewhere? Or some other annotation processor? Is FormFidoName a Java class? |
Beta Was this translation helpful? Give feedback.
-
|
So, this then is the import that causes problems... Just to clarify, this happens only within Intellij or also on the cmdline when running vanilla sbt? |
Beta Was this translation helpful? Give feedback.
-
|
I just got a random |
Beta Was this translation helpful? Give feedback.
-
|
Yes, since you use Play Java anyway (I guess), it does absolutely make no difference. |
Beta Was this translation helpful? Give feedback.
-
Sorry, missed your comment. The issues I reported were all in IntelliJ, so I'm inclined to blame it on that. I haven't had them when running sbt in my terminal. |
Beta Was this translation helpful? Give feedback.
-
I use Scala in some places (like 5% of the code), but keep it to a minimum to keep it maintainable for Java devs. There were some things I was excited about in Scala 3, like the reworked implicit stuff and trait parameters for example. But I haven't gotten used to it yet, so I can live without those things for a while 😄 |
Beta Was this translation helpful? Give feedback.
-
Does anybody else have the issue where IntelliJ is unable to properly highlight syntax or has issues recognizing imported packages after upgrading to Play 3.0?
Curiously, when I
Ctrl+ click on theorg.apache.pekko.actorimport package, it jumps to the external libraryorg.apache.pekko:pekko-actor-typed. NoAbstractActorexists in this package.Shouldn't it jump to this dependency?
I'm using:
Beta Was this translation helpful? Give feedback.
All reactions