Tobias Roeser
Tobias Roeser
Even if we don't support bumping of "provided" dependencies, this PR is still the right change, since it makes dependency resolution more consistent and allows IDEs to easily pull sources....
All classloaders I know repect the order of the entries, so we could try to put our "provided" dependencies first on the classpath. Another option would be to use version...
If you use forced versions (Maven term, I think, like `[0.11.8]`) or intervals (`[0.11.8,0.11.8]`) to pin a version, coursier will fail, if transitive selected versions don't match that range. Documentation:...
Is this about `BSP` or `GenIdea`?
Oh, I haven't realized, that IntelliJ is detecting Mill projects now, just like vscode-metals. Although, I think, the IDE should ask or at least inform the user about generating a...
I think the key to better BSP support in Mill is a BSP test suite, which we currently lack.
Could this be some unsharpness in the BSP protocol spec? Metals wants to use some location to access JVM byte-code of a specific module and it's dependencies, but never requests...
I'm not aware of any newly introduced logic that is solving this issue.
We should never mix the output paths of different modules. The issue at hand is only when a change happends after a BSP build. That is enough to see, that...
There is a high change to produce collisions hard to resolve in older external code bases or projects. E.g. > * `T[_]` -> `Task[_]` is ambiguous, since today we already...