cstamas commented on issue #1800: URL: https://github.com/apache/maven-resolver/issues/1800#issuecomment-3999232152
Yes, DefaultTrackingFileManager is one of the ugliest bits of resolver. NamedLock is defined in `maven-resolver-named-locks`, is basically an abstraction allowing one to define a "lock with name" that can share/exclude other _same named locks_. Imagine it like a `Map<String, ReentrantLock>` or alike, where key would be "name" and whoever comes for "name" would use same lock. Caching here does not help much, as this class handled files should be shared _across all the processes trying to read them_, hence they are "hot" as well. This is the last bit from Maven 3 legacy, but we cannot "fix" Local Repository even in Maven 4 timeframe, as Maven 4 must provide Maven 3 backward compatiblity. Still, in solutions like "split local repository" these "hot files" are not needed anymore, so there is hope, but, again, not everyone is able to switch to split local repo either. -- 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]
