Hi Konrad,
citing the linked web site: "Local named locks are only suited within one JVM
with a multithreaded build. Sharing a local repository between multiple Maven
processes (i.e., on a busy CI server) requires a distributed named lock!"
Best Regards
Mirko Friedenhagen
—
Sent from my mobil
Hi Konrad,
I have made no experience. We do our Maven builds in Docker containers, the .m2
directory is prefilled in the image will all dependencies managed in our
company pom, which is used by most of our applications because we ran into
problems with shared repositories. Before we used the sh
Hi Tamás,
thanks for the quick answer. Interesting solution to use extension here.
Best Regards
Mirko Friedenhagen
—
Sent from my mobile
Am 25.06.22 um 20:10 schrieb Tamás Cservenák
> Created issue https://github.com/mfriedenhagen/atend/issues/1 in your
> reproducer detailing what is
Still on creating a reproducer, however not all but only one specific internal
project seems to be affected
Best Regards
Mirko Friedenhagen
--
Sent with my mobile
Am 22.04.25 um 16:24 schrieb Mirko Friedenhagen
> Hi,
>
> I will give it a try. Stripping down our internal setup is hard. Right
Hi,
we maybe abused file activation a bit and turned on specific packaging plugins
using marker file to activate profiles defined in our company pom.
Executions and configurations are already defined in the company pom's
pluginManagement section as well.
So e.g. switching on 3 plugins we use