[ https://issues.apache.org/jira/browse/MRESOLVER-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MRESOLVER-331. ------------------------------------ Resolution: Fixed Fixed with [23cd526fe754499e1ec54ea8e618557e731fd091|https://gitbox.apache.org/repos/asf?p=maven-resolver.git;a=commit;h=802b50df5d9b7e3936f98b71496ece88da62f223]. > Make DefaultTrackingFileManager write directly to tracking files > ---------------------------------------------------------------- > > Key: MRESOLVER-331 > URL: https://issues.apache.org/jira/browse/MRESOLVER-331 > Project: Maven Resolver > Issue Type: Task > Components: Resolver > Affects Versions: 1.9.5 > Reporter: Michael Osipov > Assignee: Michael Osipov > Priority: Major > Fix For: 1.9.6 > > > Resolver recently introduced file collocation that is write to an adjecent > temp file and then atomically move to the target file. It turned out that on > Windows, when the target file is written with a high frequency the system > fails to move in time and it causes an {{AccessDeniedException}}, there is no > known workaround with current Java code. > Since tracking files are written very often for the same artifact this > creates a bottleneck. We need to resort to write to the file directly for > now, although it just affects Windows. > Pending: Report to the OpenJDK team -- This message was sent by Atlassian Jira (v8.20.10#820010)