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

Handle differently the "memoized HTTP 404" cached responses

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major
    • Resolution: Not A Problem
    • None
    • None
    • Resolver
    • None

    Description

      Currently, mvn local repo will "remember" that a repo reported 404 for artifact not present, and this fact is cached using ordinary update policy. To make mvn retry, -U is needed, that again, is too heavy handed, as it will force update always policy for everything...

      Attachments

        Issue Links

          is fixed by

          Improvement - An improvement or enhancement to an existing feature or task. MNG-7935 Expose "cache not found artifacts" configuration

          • Major - Major loss of function.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: