Closed mrdziuban closed 1 year ago
Looks like we need the same switch based on the twirl version as in the twirl repository you linked. Feel free to send a pull request.
@lefou out of curiosity, why is having scala-parser-combinators
in twirlIvyDeps
necessary? I would have guessed that it would be pulled in transitively from depending on twirl itself
@lefou out of curiosity, why is having
scala-parser-combinators
intwirlIvyDeps
necessary? I would have guessed that it would be pulled in transitively from depending on twirl itself
Yeah, that was also my first though. I don't know. You could dig in the git history, if there is some clue, or just try to remove it. Maybe, it is/was an optional dependency or it was too old for some twirl version.
Huh yeah it is optional for some reason, and tests in mill fail without it there 🤷♂️
The default
twirlIvyDeps
refer toscala-parser-combinators:1.1.2
but in the latest twirl 1.6 milestone/RC releases, they've updated to usescala-parser-combinators:2.1.0
when on scala 3.This causes a resolution error that can't be fixed just by adding the correct
scala-parser-combinators
version toivyDeps
. I was able to resolve this by overridingtwirlIvyDeps
in mybuild.sc