[GitHub] [maven] fkalinski commented on issue #310: [MNG-6843] - Parallel build fails due to missing JAR artifacts in compilePath

fkalinski commented on issue #310: URL: https://github.com/apache/maven/pull/310#issuecomment-617783528 As I have checked, the havoc is caused by ensureDependenciesAreResolved setting the artifactFilter to null on all the projects when executing "effective-pom" aggregate mojo. All

[GitHub] [maven] fkalinski commented on issue #310: [MNG-6843] - Parallel build fails due to missing JAR artifacts in compilePath

fkalinski commented on issue #310: URL: https://github.com/apache/maven/pull/310#issuecomment-617364690 I've done actually the same change and it works for me. The only difference, is not factoring the ThreadlLocals into a common class, but plainly using the three of them on the same

[GitHub] [maven] fkalinski commented on issue #310: [MNG-6843] - Parallel build fails due to missing JAR artifacts in compilePath

fkalinski commented on issue #310: URL: https://github.com/apache/maven/pull/310#issuecomment-617130914 @famod I was also going to test the ThreadLocal approach, as it seems as an easiest workaround. I have tried an approach with ThreadLocal around