-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File lock problems when running under WSL #755
Comments
I am not sure mvnd is known to work on WSL at all. @gnodet do you happen to know? Is there any stacktrace of you add |
Hi @ppalaga |
Are there maybe some logs in |
@ppalaga
if use |
|
This is a maven resolver bug. It seems similar to takari/takari-local-repository#6 |
In short, WSL2 "sells" itself as Linux, but LockFileEx is not supported. This will not work until fixed by WSL2. User could experiment by some other locking solutions like Redis backed one https://maven.apache.org/resolver/maven-resolver-named-locks-redisson/index.html Or, just as experiment, do this:
This would make mvnd use "jvm local" locking (not multi process capable), but would at least show is there any other issue on WSL2. |
Takari "shared repository" is unrelated to resolver named locks, and did suffer for bug never fixed, is not related in any way. |
Resurrecting the previous IPC SyncContext could be an idea, see https://issues.apache.org/jira/browse/MRESOLVER-342 |
To whom it may concern: According to my findings, the |
Java version
mvnd version
The text was updated successfully, but these errors were encountered: