You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/02/24 15:00:00 UTC

[jira] [Created] (MRESOLVER-329) Make IO in DefaultTrackingFileManager more robust

Tamas Cservenak created MRESOLVER-329:
-----------------------------------------

             Summary: Make IO in DefaultTrackingFileManager more robust
                 Key: MRESOLVER-329
                 URL: https://issues.apache.org/jira/browse/MRESOLVER-329
             Project: Maven Resolver
          Issue Type: Improvement
            Reporter: Tamas Cservenak
             Fix For: 1.9.6


There are couple of spots where implementation naively assumes is alone running process on this world. Several user reports suggests this is not the case, like MRESOLVER-325 or MNG-7705. Fix these spots.

Still, something is fishy, as it seems these files (all that are handled by DefaultTrackingFileManager) are not subject to locking? This needs investigation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)