[
https://issues.apache.org/jira/browse/MRESOLVER-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807404#comment-17807404
]
ASF GitHub Bot commented on MRESOLVER-264:
------------------------------------------
cstamas commented on PR #405:
URL: https://github.com/apache/maven-resolver/pull/405#issuecomment-1894317189
Right, forgot about it.
Luckily, is now generated, so if you check out master build, you'd end up
with "dirty" checkout, committed as 860973e63eed8436ab450e5aa04e1a16c9e83870
> 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: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-7
>
>
> 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.10#820010)
