-
Notifications
You must be signed in to change notification settings - Fork 634
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing setting: ensimeScalacTransformer error in sbt ensimeConfig #1425
Comments
I think we'll need an Ensime user to contribute a fix for this. If anyone would like to volunteer to fix (or even to verify whether it's still an issue in the latest versions of Ensime and Lagom) please comment here. |
@guillegr123 filed same issue ensime/ensime-sbt#401 but ensime volunteers feel that Lightbend should fix it... 😓 |
@TimMoore Can you help me understand more about the Lagom SBT build? I'm trying to contribute to fixing this compatibility issue between Lagom and Ensime. From my understanding, Lagom's SBT plugin generated some dynamic projects in The way Lagom's SBT do the build is quite unconventional. Can you enlighten me on why it's done this way inside the target directory (which may or may not be a contributing factor to this problem.)? I don't know enough about SBT... do you have any idea why target/lagom-dynamic-projects don't pick up the ensime-sbt plugin? Is it because they are not sbt subprojects? (I don't see any build.sbt file in those directories.) If these are just dynamically generated source files, why not put them under ./lib which sbt will properly recognize as unmanaged source file by default? |
Thanks for looking at it, @lightwave! This part of Lagom was developed by other people before I joined the project, so you probably understand it about as well as I do at this point. I believe the reason it uses dynamic projects is to be able to leverage sbt to manage the classpath and execution. The code that implements it is here:
The comment says:
I think the problem is likely related to that. |
HI all, I have found solution in: https://github.com/ensime/ensime-sbt/issues/401#issuecomment-425631407 It works for me. |
Nice, thanks for the pointer @vgordievskiy. Do you know if there's anything that could be changed in Lagom that would make this automatic, but without creating a dependency on Ensime? |
I don't know. I am new with the Lagom project (2 day). I just have tried to run it (with ensime for VSCode) |
Lagom Version (1.2.x / 1.3.x / etc)
1.4.6
API (Scala / Java / Neither / Both)
scala
Operating System (Ubuntu 15.10 / MacOS 10.10 / Windows 10)
MacOS 10.13.5
JDK (Oracle 1.8.0_112, OpenJDK 1.8.x, Azul Zing)
Library Dependencies
If this is an issue that involves integration with another system, include the exact version and OS of the other system, including any intermediate drivers or APIs i.e. if you connect to a PostgreSQL database, include both the version / OS of PostgreSQL and the JDBC driver version used to connect to the database.
Expected Behavior
Please describe the expected behavior of the issue, starting from the first action.
~/.sbt/1.0/plugins/plugins.sbt
build.sbt
to2.12.6
sbt
version inproject/build.properties to 1.1.6
compile
taskensimeConfig
taskensimeConfig should produce .ensime file successfully without any error.
Actual Behavior
~/.sbt/1.0/plugins/plugins.sbt
build.sbt
to2.12.6
sbt
version inproject/build.properties to 1.1.6
compile
taskensimeConfig
taskYou will see the following errors.
Reproducible Test Case
~/.sbt/1.0/plugins/plugins.sbt
build.sbt
to2.12.6
sbt
version inproject/build.properties to 1.1.6
compile
taskensimeConfig
taskThe text was updated successfully, but these errors were encountered: