[
http://jira.codehaus.org/browse/MRM-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MRM-612:
-----------------------------
Fix Version/s: 1.1
> Repository scanning does not recognize newly added artifacts if they have an
> old timestamp
> ------------------------------------------------------------------------------------------
>
> Key: MRM-612
> URL: http://jira.codehaus.org/browse/MRM-612
> Project: Archiva
> Issue Type: Bug
> Components: repository scanning
> Affects Versions: 1.0
> Environment: Win32
> Reporter: Arne Degenring
> Fix For: 1.1
>
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
