maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [maven-resolver] michael-o commented on pull request #65: [MRESOLVER-123] Provide a global locking sync context by default
Date Mon, 20 Jul 2020 19:47:08 GMT

michael-o commented on pull request #65:

   @Tibor17 I thought the same, but that's not true because map is never shared, but scoped
to the current thread. So the access is sequential. The `FileLockManager` has to be theadsafe.
Put if absent would be necessary, if and only if the map would be in the factory and passed
down to instances. Then I would agree with you.

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.

For queries about this service, please contact Infrastructure at:

View raw message