You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2023/02/24 09:18:00 UTC
[jira] [Commented] (MRESOLVER-264) Make file-lock the default locking
[ https://issues.apache.org/jira/browse/MRESOLVER-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693091#comment-17693091 ]
Michael Osipov commented on MRESOLVER-264:
------------------------------------------
I still think this is wrong, especially in a minor version.
> 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: 1.10.0
>
>
> 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)