[
https://issues.apache.org/jira/browse/MNG-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17425406#comment-17425406
]
Michael Osipov commented on MNG-7285:
-------------------------------------
If you can reproduce the issue, you can try to revert those two commits by
Falko Modler and see whether your issue is fixed. However, I guess a revert
will break other things .-(
> [Regression] MavenProject.getArtifacts() not returning correct value across
> multiple threads
> --------------------------------------------------------------------------------------------
>
> Key: MNG-7285
> URL: https://issues.apache.org/jira/browse/MNG-7285
> Project: Maven
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.8.3
> Reporter: Mickael Istria
> Priority: Critical
>
> Patch for MNG-6843 seems to cause that when trying to use
> MavenProject.getArtifacts() across different threads, some of them get an
> incorrect result.
> This cause an issue in m2e where we schedule a lot of work and don't have
> much control over which thread will do the work (there is a thread pool);
> we've faced several regressions because of this issue when trying to adopt
> 3.8.3 from 3.8.1. More details at
> [https://github.com/eclipse-m2e/m2e-core/pull/346|https://github.com/eclipse-m2e/m2e-core/pull/350]
> ,
> [https://github.com/eclipse-m2e/m2e-core/pull/347|https://github.com/eclipse-m2e/m2e-core/pull/350]
> and [https://github.com/eclipse-m2e/m2e-core/pull/350] .
> I'll try to capture it in a test case for maven repo in the next days.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
