[
https://issues.apache.org/jira/browse/MNG-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902940#comment-16902940
]
Zakharov Denis commented on MNG-2802:
-------------------------------------
I'm not 100% sure but i have put Takari Extension into lib/ext folder and
continue to get errors like this yet:
15:11:13.552 [INFO] --------------------------------[ war
]---------------------------------
[|http://fobo-build01.corp.mvideo.ru:8082/jenkins/blue/organizations/jenkins/Build%2FBuildWincash/detail/release%2F20.0.0/72/pipeline/#step-424-log-62]15:11:13.617
[WARNING] The POM for ******:********:jar:20.0.0 is invalid, transitive
dependencies (if any) will not be available, enable debug logging for more
details
It means that file was changed from another maven process.
Mb something changed for years but it doesn't work for me with maven 3.6.1
It will be very appreciate if you add concurrent-safe access to local
repository in maven core functionality
> Concurrent-safe access to local Maven repository
> ------------------------------------------------
>
> Key: MNG-2802
> URL: https://issues.apache.org/jira/browse/MNG-2802
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Reporter: Stepan Roh
> Assignee: John Casey
> Priority: Major
> Fix For: Issues to be reviewed for 3.x
>
>
> It seems that access to local Maven repository is not concurrent-safe that is
> multiple Mavens running in parallel may damage contents of local Maven
> repository. It would be a nice improvement, because sharing of local
> repository will lower the need for contacting any other repository. I know
> that Maven proxy can be used, but that adds another layer which may
> unnecessarily stress the machine it runs on.
> *NOTE:*
> http://takari.io/book/30-team-maven.html#concurrent-safe-local-repository is
> a Takari Extension for Apache Maven that introduces a concurrent-safe
> local-repository.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
