Open jgogstad opened 4 years ago
Thanks for reporting! bloopCompile
is part of an experimental feature and is currently disabled by default. I wouldn't recommend using it currently.
Closing this, since bloopCompile is not supposed to work currently. Please use the CLI, Metals or Intellij with BSP. More info about the CLI can be found on the Bloop webpage here.
Popping in here. I really don't think we should close this without some type of action signifying that this isn't supported. I'm trying to do some work on the plugin atm, and running through the commands trying to get a better understanding of what is all happening. When playing around with this one, I don't actually think we should just leave it as is in its current state.
Being accessible to users, but also knowingly not working can be frustrating to users. What do you think of either opening this back up as an issue that bloopCompile
doesn't work, somewhere documenting it clearly that it's not to be used, or simply removing it from the plugin if it truly isn't ready to be used. Let me know how I can help with this.
@ckipp01 you are right, I would opt for throwing that setting out for now, but I am not exactly sure about the reasons for including it.
Running the task
bloopCompile
doesn't work on a new sbt project according to scala/scala-seed.g8, it fails withThis happens on macOS Catalina, but it's also reproducible in the docker image
eed3si9n/sbt
: