[
https://issues.apache.org/jira/browse/MRESOLVER-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558561#comment-17558561
]
Michael Osipov edited comment on MRESOLVER-264 at 6/24/22 4:11 PM:
-------------------------------------------------------------------
Not by Java means:
* Try an advisory lock: Get an exception like in MNG-5838. That would be awesome
* Try NFSv3 lock or incompletely NFSv4 lock and suffer in pain
* Can't tell for Lustre, Ceph, Gluster, etc.
Upshot: I see no portable way doing this. Even worse, with broken locking
people will get affect we won't be able to understand and analyze.
was (Author: michael-o):
Not by Java means:
* Try an advisory lock: Get an exception like in MNG-5838. That would be awesome
* Try NFSv3 lock or incompletely NFSv4 lock and suffer in pain
* Can't tell for Lustre, Ceph, Gluster, etc.
> 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)
