Uploaded image for project: 'Maven Resolver'
  1. Maven Resolver
  2. MRESOLVER-329

Make IO in DefaultTrackingFileManager more robust

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • None
    • Resolver
    • None

    Description

      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.

      Attachments

        Issue Links

          fixes

          Bug - A problem which impairs or prevents the functions of the product. MNG-7705 Sporadic failures on multiple builds sharing the same local repo when writing the .lastUpdated file

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MRESOLVER-325 [REGRESSION] Suddenly seeing I/O errors under windows aborting the build

          • Major - Major loss of function.
          • Closed
          links to

          Web Link GitHub Pull Request #257

          Web Link GitHub Pull Request #260

          Activity

            People

              cstamas Tamas Cservenak
              cstamas Tamas Cservenak
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: