[MRESOLVER-331] Make DefaultTrackingFileManager write directly to tracking files

[jira-importer]

Michael Osipov opened MRESOLVER-331 and commented

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

---

Affects: 1.9.5

Issue Links:

• MRESOLVER-325 [REGRESSION] Suddenly seeing I/O errors under windows aborting the build
  ("fixes")

Remote Links:

• GitHub Pull Request #259
  
• Report with OpenJDK team
  

[jira-importer]

Michael Osipov commented

Fixed with 23cd526fe754499e1ec54ea8e618557e731fd091.

[jira-importer]

Michael Osipov commented

Issue logged: https://bugs.openjdk.org/browse/JDK-8303225