I have already created https://issues.apache.org/jira/browse/MSHADE-467
and also might have a fix. Please watch the issue and the soon to be
created PR to know when to get ready to re-test this with you real
project.
--
Alexander Kriegisch
https://scrum-master.de
Alexander Kriegisch schrieb am
Hi Estelle.
Thanks for the reproducer, great job!
When the mojo is running concurrently, each thread gets its own mojo
instance. I.e., there can only be a problem if
a) the mojo uses static variables in a thread-unsafe way or
b) the mojo uses some shared state from Maven itself.
Case (a)
I think Estelle's mail lacked the context so I added it below. She made a
reproducer for a probable bug regarding missing exclusions from the
dependency-reduced-pom.xml in recent versions of the Shade plugin when run
in parrallel. Thanks Estelle !
Francois
Le ven. 19 janv. 2024 à 18:37, Estelle
Hello !
I work with François. Here's a quite simple example reproducing the problem
: https://github.com/stl543/shadeMT
It has a parent pom so the 4 child modules have strictly the same
configuration apart from their artifactId.
The following command will give you results varying between 12, 16
