Skip to content
This repository was archived by the owner on Feb 18, 2025. It is now read-only.

Wrong path under WSL #44

Open
ColOfAbRiX opened this issue Nov 20, 2020 · 0 comments
Open

Wrong path under WSL #44

ColOfAbRiX opened this issue Nov 20, 2020 · 0 comments

Comments

@ColOfAbRiX
Copy link

ColOfAbRiX commented Nov 20, 2020

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:

$ sbt
...
[info] loading project definition from /mnt/c/Users/JamesSmith/Projects/myproject/project
[error] java.nio.file.NoSuchFileException: C:\Users\JamesSmith\AppData\Local\Coursier\cache\v1\https\repo1.maven.org\maven2\com\typesafe\config\1.3.3\config-1.3.3.jar
...
[error] (Compile / bloopGenerate) java.nio.file.NoSuchFileException: C:\Users\JamesSmith\AppData\Local\Coursier\cache\v1\https\repo1.maven.org\maven2\com\typesafe\config\1.3.3\config-1.3.3.jar

Expected behaviour

Coursier should use a WSL path when working inside WSL

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants