[
https://issues.apache.org/jira/browse/MDEP-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902383#comment-16902383
]
Padma Guruvelli edited comment on MDEP-657 at 8/7/19 6:16 PM:
--------------------------------------------------------------
I don't have complete understanding of maven concepts, I was in an assumption
the sections defined in dependencies are using dependency plugin , Is that not
the case?
Apologies for repeating the answers .
We cannot use clean package as we have integration tests that needs to be
installed locally .
But the error would not be resolve with package .
As the above failure is while downloading dependencies in local m2 .
The issue happens if we have the flags -U -T 2C .
This issue can be reproduced if we have two modules downloading same dependency
and run with above flags with clean m2 directory.
Based on what I understand from the error seems, when two modules that are
running in parallel and both are downloading same dependency, one locks it when
it is in process and if other tries at the same time, it fails with above error.
was (Author: padmag):
I don't have complete understanding of maven concepts, I was in an assumption
the sections defined in dependencies are using dependency plugin , Is that not
the case?
Apologies for repeating the answers .
We cannot use clean package and we have integration tests that needs to be
installed locally .
But the error would not be resolve with package .
As the above failure is while downloading dependencies in local m2 .
The issue happens if we have the flags -U -T 2C .
This issue can be reproduced if we have two modules downloading same dependency
and run with above flags with clean m2 directory.
Based on what I understand from the error seems, when two modules that are
running in parallel and both are downloading same dependency, one locks it when
it is in process and if other tries at the same time, it fails with above error.
> Maven - Failing when two modules have same dependency and both trying to
> download the dependency at the same time when Parallel flag is enabled.
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MDEP-657
> URL: https://issues.apache.org/jira/browse/MDEP-657
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Environment: Maven 3.6.1
> Reporter: Padma Guruvelli
> Priority: Major
>
> Maven Version 3.6.1
> command : mvn -U -T 2C -DskipTests=true clean install -s settings.xml
> We have several modules with same dependency and it is failing when two are
> downloading same dependency at the same time with below error.
> if we remove parallel flag it will go through. But the build will be very
> long.
> Ideally it should wait and not fail?
>
> [ERROR] Failed to execute goal on project content-model: Could not resolve
> dependencies for project com.gehc.ei.zfp:content-model:jar:6011.0.1.8270:
> Failed to collect dependencies at
> com.gehc.ei.zfp:ei-logging-service:jar:6011.0.1.8109 ->
> com.gehc.ei.zfp:atna-log-appender:jar:6011.0.1.8109: Failed to read artifact
> descriptor for com.gehc.ei.zfp:atna-log-appender:jar:6011.0.1.8109: Could not
> transfer artifact com.gehc.ei.zfp:atna-log-appender:pom:6011.0.1.8109 from/to
> central
> (xxxx[/artifactory/maven-zfp-all|https://dev-artifactory.cloud.health.ge.com/artifactory/maven-zfp-all]):
>
> C:\Users\ecagent\.m2\repository\com\gehc\ei\zfp\atna-log-appender\6011.0.1.8109\atna-log-appender-6011.0.1.8109.pom.part.lock
> (The process cannot access the file because it is being used by another
> process) -> [Help 1]
> Any idea why it is behaving this way?
> Regards,
> Padma
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
