Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-26214

Orphaned maven-metadata files not cleaned up

    Details

    • Type: Bug
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.29.0, 3.30.0
    • Fix Version/s: None
    • Component/s: Cleanup, Maven
    • Labels:
    • Notability:
      3

      Description

      On NXRM 3.29, orphaned maven-metadata.xml, sha1, md5, sha256 and sha512 files brought over from an upgrade are not removed by cleanup policies.

      To reproduce

      1. On NXRM version pre 3.29, run a gradle deploy to a maven repo with a permissive layout.
      2. Configure and run a cleanup policy against the maven repo e.g. based on published date and confirm that all files except the sha256 and sha512 files are removed.
      3. Upgrade the instance to 3.29 and run cleanup policy again.

      Expected

      Orphaned maven-metadata.xml, sha1, md5, sha256 and sha512 files are removed.

      Actual

      Orphaned maven-metadata.xml, sha1, md5, sha256 and sha512 files are not removed.

      Workaround

      Manually delete the orphaned files/directories.

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              hardeepn Hardeep Nagra
              Last Updated By:
              Joe Tom Joe Tom
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Date of First Response:

                  tigCommentSecurity.panel-title