maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] [Commented] (MDEP-442) Failed to access file due to locked access when using more than one Maven worker thread
Date Thu, 08 Dec 2016 21:40:59 GMT


Robert Scholte commented on MDEP-442:

[~krosenvold] I guess you tried to fix this but for unknown reason reverted it (
Current plexus-utils (3.0.24) uses java.nio.channels.FileChannel to copy, you would expect
that this should be enough, right?

> Failed to access file due to locked access when using more than one Maven worker thread
> ---------------------------------------------------------------------------------------
>                 Key: MDEP-442
>                 URL:
>             Project: Maven Dependency Plugin
>          Issue Type: Bug
>          Components: copy
>    Affects Versions: 2.8
>         Environment: MVN 3.0.4, JDK 1.7, Win 7 Pro SP1 64 Bit
>            Reporter: Markus Karg
>            Priority: Critical
>             Fix For: waiting-for-feedback
>         Attachments:,
> My multi-module POM contains of ten modules. Each of that modules does the same: Invoke
the 'copy' goal of the dependency plugin. The idea is to have ten copies of the identical
source, which then will end up in ten different targets by getting furthere processed.
> As long as I do not use more than one Maven worker thread, everything works well always.
But when using -T 5 to have five worker threads, rather often the reactor fails because the
source file (!) is locked:
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:copy
(copy) on project MYARTIFACT: Unable to resolve artifact. Could not transfer artifact mygroup:myartifact:dll:4.36.1-20140415.143537-37
from/to nexus (http://nexus/nexus/content/groups/public): C:\Users\jenkins.QUIPSY\.m2\repository\mygroup\myartifact\4.36.1-SNAPSHOT\myartifact-4.36.1-20140415.143537-37.dll
(The process cannot access the file, because it is in use by another process)
> {noformat}
> So it seems that the 'copy' task actually is locking the source file, which is not multi-threading-compatible.
Hence, either that is a bug and should get fixed, or it is on purpose, then this goal has
to be marked as non-multithreading-able.

This message was sent by Atlassian JIRA

View raw message