slachiewicz commented on issue #1375: URL: https://github.com/apache/maven-resolver/issues/1375#issuecomment-5485362790
The underlying corruption mechanism was fixed in stages: serialized tracking-file writes (MRESOLVER-177, 1.7.x, shipped with Maven 3.8.4 — confirmed earlier in this thread that the problem vanished there), file locking on tracking files (MRESOLVER-364, 1.9.11) and the modern TrackingFileManager with per-path JVM mutex plus OS file locks (PR #1814, 2.0.17). No reproducible defect on any version newer than 2021 has surfaced in this thread. Two notes for anyone arriving from a search: (1) sharing one local repository between multiple concurrent processes (e.g. CI agents) requires named locks — maven-resolver-named-locks has been the in-JVM default since Maven 3.9.0, with file-based and other variants for cross-process use; (2) an already-corrupt tracking file still fails fast by design — remove it (see the cleanup command earlier in this thread). Closing as fixed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
