Closed pzygielo closed 4 months ago
On second run of CI all was fine.
Unfortunately the first (failed) run was without -X
flag, so I can't share stack trace now.
Found this: https://issues.apache.org/jira/browse/MNG-7868
The exception could come from: https://github.com/s4u/pgpverify-maven-plugin/blob/f5fbc245e64091a41ba0926a6958b98bf0b29eb3/maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/synccontext/named/NamedLockFactoryAdapter.java#L219 (resolver 1.9.20 - used by maven)
Describe the bug
In the maven (3.9.7 + Java Corretto 21.0.3-9.1/x64, ubuntu) project built with
-T 2C
I've got:At https://www.simplify4u.org/pgpverify-maven-plugin/check-mojo.html the goal is marked as thread-safe and I've never encountered issues with that before.
To Reproduce TBD
Expected behavior
Additional context As for now I don't know if related: happened after upgrading maven-shade-plugin from 3.5.3 to 3.6.0.