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)
- shade 3.2.0 : ok
> - shade 3.1.0 : ok
>
> Do you think I should open an issue directly with the shade plugin ?
> Best regards,
> Estelle
>
-- Forwarded message -
De : Alexander Kriegisch
Date: ven. 12 janv. 2024 à 03:21
Subject: Re: Random missing exclusions in
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
Hello François.
I am not a committer in any Apache project, but I have contributed to
Shade here and there.
A reproducer would certainly help, so please post GitHub link, as soon
as you have one. If it is clearly reproducible, it might also be wort
opening an issue to have something to commit
Hello,
First let me wish the Maven community a happy new year.
I recently faced a problem with the shade plugin generating randomly
different dependency-reduced-pom.xml.
The difference lies in exclusions defined in miscellaneous dependencies
randomly being missing in the pom.
This part of the
