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

Resolver checksum calculation should be driven by layout

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.8.0
    • Resolver
    • None

    Description

      Currently, whether connector calculates checksums or not is driven by Layout.ChecksumLocation, but this is wrong, as some artifacts (like signatures) may not have checksum locations returned by layout, and hence, is shutting down complete checksum calculation. That, on the other hand, fails remote transport in case of FAIL checksum policy.
      This change alone does NOT fix special cases like "resolving from remote signature", but makes a step to fix it.

      The fact that Layout.ChecksumLocation is empty does not mean anything else, that resolver should not expect on remote checksum (REMOTE_EXTERNAL), but not shut down completely checksum validation as other mechanisms (REMOTE_INCLUDED or PROVIDED) should still kick in, if applicable.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            cstamas Tamás Cservenák
            cstamas Tamás Cservenák
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment