vmunier / sbt-web-scalajs

SBT plugin to use Scala.js along with any sbt-web server.
Apache License 2.0
194 stars 30 forks source link

v1.3.0 no such method error on SbtWeb$.withActorRefFactory #193

Open bwbecker opened 9 months ago

bwbecker commented 9 months ago

I'm in the process of updating dependencies for my play+scala.js project and ran into an issue with sbt-web-scalajs. I updated from v 1.1.0 to 1.3.0 and my compiles started failing:

...
[warn] 15 warnings found
[info] Fast optimizing /Users/bwbecker/oat/src/oat3/_browser/target/scala-2.13/browser-fastopt
[info] LESS compiling on 5 source(s)
[info] LESS compiling on 1 source(s)
[error] stack trace is suppressed; run last wapp / Web-assets / less for the full output
[error] stack trace is suppressed; run last wsvc / Web-assets / less for the full output
[error] (wapp / Web-assets / less) java.lang.NoSuchMethodError: 'java.lang.Object com.typesafe.sbt.web.SbtWeb$.withActorRefFactory(sbt.State, java.lang.String, scala.Function1)'
[error] (wsvc / Web-assets / less) java.lang.NoSuchMethodError: 'java.lang.Object com.typesafe.sbt.web.SbtWeb$.withActorRefFactory(sbt.State, java.lang.String, scala.Function1)'
[error] Total time: 35 s, completed Jan. 25, 2024, 12:14:26 p.m.
[oat] $ last wsvc / Web-assets / less
[error] Expected configuration
[error] Expected ':'
[error] Expected key
[error] Not a valid key: Web-assets (similar: assets)
[error] last wsvc / Web-assets / less
[error]                       ^
[oat] $ last wsvc / assets / less
[oat] $ 

This happens with java 11 as well as java 17. I'm using sbt.version=1.9.8 and scala 2.13.12.

If I remove all the target directories, change back to 1.1.0 and recompile, the problem goes away.

I tried the same with your play-scalajs seed but could not reproduce the problem.

The build where I have the issue also has

addSbtPlugin("com.typesafe.sbt" % "sbt-less"   % "1.1.2")

I tried adding that to the play-scalajs seed but was again unable to reproduce the problem.

I realize there's probably not much that can be done with this, given the lack of a small project that reproduces the issue. But thought I'd register it just in case...