You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when exporting Bloop configuration files from sbt, the provided dependencies will be on compile classpath, but not on runtime classpath. This is inconvenient for local debugging, since we will run without jars needed by the application.
This actually is valid behaviour since -> A dependency with this scope is added to the classpath used for compilation and test, but not the runtime classpath, but is very inconvenient for users.
I would opt to include provided deps anyways in the runtime classpath, but I wasn't able to figure it out.
Currently, when exporting Bloop configuration files from sbt, the provided dependencies will be on compile classpath, but not on runtime classpath. This is inconvenient for local debugging, since we will run without jars needed by the application.
This actually is valid behaviour since ->
A dependency with this scope is added to the classpath used for compilation and test, but not the runtime classpath
, but is very inconvenient for users.I would opt to include provided deps anyways in the runtime classpath, but I wasn't able to figure it out.
Originally opened in scalameta/metals#5943
Runtime classpath is set here https://github.com/scalacenter/bloop/blob/main/integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala#L791
The text was updated successfully, but these errors were encountered: