cstamas commented on PR #1812:
URL: https://github.com/apache/maven-resolver/pull/1812#issuecomment-4117562008

   Yes it is, but observe this: 
https://github.com/apache/maven-resolver/issues/1800#issuecomment-3979928022
   
   Summary:
   * maven2 locked the file itself
   * maven3.x continued doing the same to preserve backward compat (so until 
this point they could co-exist working on same local repo)
   * maven3.10, if change to named locks (they do not lock the subject file, 
they are pure "advisory locking") this breaks


-- 
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]

Reply via email to