[
https://issues.apache.org/jira/browse/MRESOLVER-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17557612#comment-17557612
]
Tamás Cservenák edited comment on MRESOLVER-264 at 6/22/22 6:43 PM:
--------------------------------------------------------------------
Well, I bet very few people work on non-locking FS, in a sixpack? So why force
our majority of user base to "tweak" (to be able to run mvn in several Terminal
windows simultaneously), instead let those people on super computers (not our
every day users, are they?) to change to in-jvm lock?
I mean, in related issue the direct lock call was the issue. Today, one can
remediate that by setting lock factory to some "local" or even "none", and
error is gone.
was (Author: cstamas):
Well, I bet very few people work on non-locking FS, in a sixpack? So why force
our majority of user base to "tweak", instead let those people on super
computers (not our every day users, are they?) to set up in-jvm lock?
I mean, in related issue the direct lock call was the issue. Today, one can
remediate that by setting lock factory to some "local" or even "none", and
error is gone.
> Make file-lock the default locking
> ----------------------------------
>
> Key: MRESOLVER-264
> URL: https://issues.apache.org/jira/browse/MRESOLVER-264
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamás Cservenák
> Assignee: Tamás Cservenák
> Priority: Major
> Fix For: 1.8.2
>
>
> Default locking in Resolver is RW locks, that is only in-JVM (so covers the
> multi threaded case). Simply, if users use Maven concurrently from different
> terminal windows, they still can end up with corrupted local repository.
> Hence, IMHO the default should be {{{}file-lock{}}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
