[jira] [Commented] (MNG-7545) CLONE - Multithreaded building can create bad files for downloaded artifacts in local repository

["Michael Osipov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-7545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609063#comment-17609063 ] 

Michael Osipov commented on MNG-7545:
-------------------------------------

Read: https://maven.apache.org/resolver/maven-3.8.x.html

> CLONE - Multithreaded building can create bad files for downloaded artifacts in local repository
> ------------------------------------------------------------------------------------------------
>
>                 Key: MNG-7545
>                 URL: https://issues.apache.org/jira/browse/MNG-7545
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 3.8.3
>            Reporter: liuchangcheng
>            Assignee: Michael Osipov
>            Priority: Major
>
> Within a parallel build, modules A and B can start at the same time and decide at the same time that they need to download artifact X. Since X is not available locally, both can start download of X. Both will download X and both will try to write the file for X to disk.
> On Windows platforms, one of them can fail with file locking problems. On Unixes the contents of the written file can be non-deterministic.
> This issue is related to MNG-2802 in the sense that it can create a corrupted artifact file in the local repository, and it can happen to ANY file written. But as opposed to MNG-2802 the synhronization needed to fix this issue is basically only within a single running maven process, so regular java mechanisms can apply, whereas MNG-2802 probably needs to use a totally different solution space.
>  
> is this issue fixed?
> we are still facing this problem with maven 3.8.3



--
This message was sent by Atlassian Jira
(v8.20.10#820010)