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've encountered this issue while using SBT and coursier and I've opened the issue there too: coursier/coursier#1919
Issue
I'm using coursier with SBT under a WSL environment. After updating SBT from version 1.3.13 to 1.4.1 coursier is looking at the wrong path for the cache, specifically it's using a windows path, and dependency resolution fails.
Environment
OS: Windows 10, but running under WSL/Ubuntu 18.04.4 LTS SBT: 1.4.1 (don't know how to check coursier version) JVM: Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
Current behaviour
Under WSL, coursier uses a Windows path to resolve the cache:
I've encountered this issue while using SBT and coursier and I've opened the issue there too: coursier/coursier#1919
Issue
I'm using coursier with SBT under a WSL environment. After updating SBT from version 1.3.13 to 1.4.1 coursier is looking at the wrong path for the cache, specifically it's using a windows path, and dependency resolution fails.
Environment
OS: Windows 10, but running under WSL/Ubuntu 18.04.4 LTS
SBT: 1.4.1 (don't know how to check coursier version)
JVM: Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
Current behaviour
Under WSL, coursier uses a Windows path to resolve the cache:
Expected behaviour
Coursier should use a WSL path when working inside WSL
The text was updated successfully, but these errors were encountered: