Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.0.2
-
Fix Version/s: 1.1.2
-
Component/s: repository scanning
-
Labels:None
-
Patch Submitted:Yes
-
Number of attachments :
Description
If you pre-configure a populated repository, Archiva does not display the content immediately when you start the application.
I think it should scan and index the repositories on startup, or possibly on the 'first' startup (when the database and index are empty.)
Attachments
Activity
Hi Gwen, thanks for the patch!
I took a quick look at it and it looks good to me 
Just one comment though, maybe we could check if a repository has already been scanned in a different way? I'm a little hesitant on relying on existence of the .index directory to see if the repo has already been scanned as the indexing consumer can be disabled. Wdyt?
Just one comment though, maybe we could check if a repository has already been scanned in a different way? I'm a little hesitant on relying on existence of the .index directory to see if the repo has already been scanned as the indexing consumer can be disabled. Wdyt? Yeah it will still scan repositories if the indexing consumer will be disabled.
I'll try a different way on checking the repository if it has been scanned or not.
Thanks
Here's another patch that checks if a repository has been scanned, by getting there ids and placing them in a list.
Thanks Miss Deng
I'm concerned about throwing in a scan-on-startup due to the cost, and it's not trivial to detect whether a repository has already been scanned at that point of initialisation. Will take a closer look in a future version but I think this is minor.