Timeline for answer to Plugin compilation using wrong Scala version by Mario Galic
Current License: CC BY-SA 4.0
Post Revisions
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 1, 2021 at 15:05 | comment | added | Terry Dactyl | Thanks for your help guys. It appears that the relevant file was located under project but not used by project however it was also used elsewhere and therefore compiled using the meta-build and proper-build versions (2.12 and 2.13). Problem now solved. | |
| Apr 1, 2021 at 14:47 | comment | added | Luis Miguel Mejía Suárez |
@TereyDactyl project/build.sbt
|
|
| Apr 1, 2021 at 14:01 | comment | added | Terry Dactyl | So - from which file would I control the scala version? | |
| Apr 1, 2021 at 13:49 | comment | added | Mario Galic | @TerryDactyl Indeed your local custom made sbt plugins as well as downloaded sbt plugins must use the same scala version of the meta project. | |
| Apr 1, 2021 at 13:37 | comment | added | Terry Dactyl | Is the meta project also responsible for the compilation of any locally built (i.e non imported) plugins? I believe this is what is happening because sbt itself is failing during the incremental compile stage. | |
| Apr 1, 2021 at 13:23 | history | edited | Mario Galic | CC BY-SA 4.0 |
deleted 1 character in body
|
| Apr 1, 2021 at 13:18 | history | answered | Mario Galic | CC BY-SA 4.0 |