Uploaded image for project: 'Archiva'
  1. Archiva
  2. MRM-612

Repository scanning does not recognize newly added artifacts if they have an old timestamp

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0
    • Fix Version/s: 1.3
    • Component/s: repository scanning
    • Labels:
      None
    • Environment:
      Win32

      Description

      After starting up a fresh instance with default configuration, I copied parts of my existing repository to Archiva's default internal repository. Then I used the "Scan Repository Now" button on the repository administration page. Afterwards, all artifacts were visible on the "Browse" page. So far so good.

      I then copied some more groups of my existing repo to Archiva's default internal repository, and used "Scan Repository Now" once again. But this time, the "Browse" page did not show the newly added groups. This was quite surprising, as the log output of RepositoryScanner clearly showed that Archiva DID walk over these new artifacts, without errors or warnings. I tried to use the "Update Database Now" button, but still no effect.

      I finally touched one of the POM files in the missing groups, i.e. I gave the POM file a new timestamp. After doing "Scan Repository Now" again, the artifact appeared on the Browse page.

      As discussed on http://www.nabble.com/Repository-scanning-problem-in-1.0--tf4897121.html#a14132393

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                oching Maria Odea B. Ching
                Reporter:
                arned Arne Degenring
              • Votes:
                6 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: