ascheman commented on issue #2017: URL: https://github.com/apache/maven-resolver/issues/2017#issuecomment-5184611729
Closing this: the reported failure turned out to be the central-publishing plugin using the local repository as a staging tree (Maven-2 `maven-compat` bits), not a resolver bug. `file-lock` at the repo root is by design correct — it protects the local repo against concurrent access and, unlike an existence-based lock, auto-releases on process death. Full analysis (and the POSIX/Windows cleanup nuance) is on the users@ thread: https://lists.apache.org/thread/1trdtdct2glycrzqo6xhbryns5o5pxno Thanks @cstamas and @elharo for setting it straight. If the Windows leftover-file cleanup is worth pursuing on its own, happy to help — but that's separate from this report. -- 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]
