You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2014/01/23 21:43:49 UTC

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

     [ https://jira.codehaus.org/browse/MNG-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl updated MNG-4706:
-------------------------------

    Fix Version/s:     (was: Issues to be reviewed for 3.x)
                   Issues to be reviewed for 4.x
    
> Multithreaded building can create bad files for downloaded artifacts in local repository
> ----------------------------------------------------------------------------------------
>
>                 Key: MNG-4706
>                 URL: https://jira.codehaus.org/browse/MNG-4706
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 3.0-beta-1
>            Reporter: Kristian Rosenvold
>            Assignee: Kristian Rosenvold
>             Fix For: Issues to be reviewed for 4.x
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira