ThisBuild / scalaVersion := "2.13.2"already there
2.11.12so I get another annoying message too.
Any idea why bloop would loose track of a directory under
bloop-bsp-clients-classes? I'm getting errors running
bloop compile where it complains that a file is not found:
And it turns out "classes-Metals-hFsrTRk0QjCJiRjDo1RBzQ==" does not exist. I'm running metals in VS Code and the bloop CLI at the same time, if that makes a difference.
Hi all, I'm having problem compiling my integration test with bloop. I have no problem with sbt. I share test fixtures between unit tests and integration tests. I have this in my
build.sbt for enabling the share:
.settings( dependencyClasspath in IntegrationTest := (dependencyClasspath in IntegrationTest).value ++ (exportedProducts in Test).value )
I'm a noob with bloop and I used
sbt bloopInstall to generate the bloop projects. I wonder maybe the sharing is a special case and requires some customization in the bloop projects. Please advise. Thanks.
I have a project that with code like:
dependsOn( anotherProject % "optional->compile" )
These dependencies are missing from the generated (sbt
bloopInstall) bloop configurations. I tried adding this using the
inConfig(Optional)(bloopSettings) pattern. Which did not work: The optional config has no
productDirectories. From a developer perspective, I'd expect these to be treated like compile dependencies. Which, assuming correct so far, requires changing: https://github.com/scalacenter/bloop/blob/a35149836cfebcd6041f84fc17a2a2b896dbcb33/integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala#L505