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
I would say, since it's "unmanaged", it's reasonable for you to manage it manually and don't have some defaults, which may break someones else workflow.
Hmm, but the current behavior is different between mill and bloop when running the app. With mill, it runs fine (all classpath jars are present), with bloop it crahes with (in my case) NoClassDefFoundError.
I also find it hard to imagine the kind of situation where adding a transitive jar to bloop output (making the classpath complete) can actually break a workflow.
mill/contrib/bloop/src/mill/contrib/bloop/BloopImpl.scala
Lines 215 to 219 in 80f2a88
This doesn't contain the
unmanagedClasspath
jars of the module being depended on.Workaround (for me): the depending module can override its
unmanagedClasspath
to manually include everything.The text was updated successfully, but these errors were encountered: