[MNG-7285] [Regression] MavenProject.getArtifacts() not returning correct value across multiple threads

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-1, 3.8.2, 3.8.3
• Fix Version/s: 3.8.4, 4.0.0-alpha-2, 4.0.0
• Component/s: Core
• Assignee: Michael Osipov
• Reporter: Mickael Istria
• Created: 06/Oct/21 20:34
• Updated: 27/Nov/22 10:08
• Resolved: 22/Oct/21 20:22

Description

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/347 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.

Issue Links

• is broken by: MNG-6843 Parallel build fails due to missing JAR artifacts in compilePath
• is fixed by: MNG-7312 Revert ThreadLocal approach from MNG-6843 and MNG-7251
• is related to: MNG-7156 Parallel build can cause issues between clean and forked goals
• links to: GitHub Pull Request #570
• links to: GitHub Pull Request #578