-
Notifications
You must be signed in to change notification settings - Fork 337
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
Compilation triggered repeatedly with no results using SBT BSP #6896
Comments
The infinite compilation is caused by code generation. When code in |
I wonder if this is not an issue with sbt. Does using Most of the generated sources are marked as such by sbt itself, any idea why this one isn't? |
I think it a mistake in the project setup. According to SBT docs: A source generation task should generate sources in a subdirectory of sourceManaged and return a sequence of files generated. For sbt:root> show core/sourceManaged
[info] .../smithy4s/modules/core/target/jvm-2.13/src_managed which is also correctly marked as generated in the build target: .../smithy4s/modules/core/target/jvm-2.13/src_managed/main/* (generated) But file
is also a generated file. |
Describe the bug
The branch is special because it enables a plugin that computes a single setting - bspEnabled: https://github.com/indoorvivants/sbt-bspquery/blob/main/mod/sbt-plugin/src/main/scala/SbtBspQueryPlugin.scala#L27, conditionally disabling some projects from the import
The BSP logs don't offer any insights
Expected behavior
The project is imported normally and compiled only once
Operating system
macOS
Editor/Extension
VS Code
Version of Metals
v1.4.0
Extra context or search terms
sbt bsp compilation trigger
The text was updated successfully, but these errors were encountered: