[MRM-1056] Option to force scanning of an artifact/repository regardless of file dates

o update docs when scanning repositories and upgrading archiva to newer versions



git-svn-id: https://svn.apache.org/repos/asf/archiva/trunk@816092 13f79535-47bb-0310-9956-ffa450edef68

4 files changed, 12 insertions, 3 deletions

diff --git a/archiva-docs/src/site/apt/adminguide/repositories.apt b/archiva-docs/src/site/apt/adminguide/repositories.apt
index 7a754652f..efa95c024 100644
--- a/archiva-docs/src/site/apt/adminguide/repositories.apt
+++ b/archiva-docs/src/site/apt/adminguide/repositories.apt
@@ -106,7 +106,14 @@ http://[URL TO ARCHIVA]/repository/[REPOSITORY ID] (e.g. http://localhost:8080/a
 * Scanning a Repository
  
   Repository scan can be executed on schedule or it can be explicitly executed by clicking the 'Scan Repository Now' button in 
-  the repositories page. For every artifact found by the repository scanner, processing is done on this artifact by different
+  the repositories page. By default, Archiva only processes new artifacts in the repository with respect to the last run of the
+  repository scanner. Meaning that if the artifact's last modified date is newer than the last repository scan, then the artifact
+  will be processed. Otherwise, it will be skipped. You can override this behavior and force Archiva to process all artifacts regardless
+  of its age by ticking the 'Process All Artifacts' checkbox in the repositories page and clicking the 'Scan Repository Now' button.
+
+[../images/repositories.png] Repositories
+
+  For every artifact found by the repository scanner, processing is done on this artifact by different
   consumers. Examples of the processing done are: indexing, repository purge and database update. Details about consumers are 
   available in the {{{consumers.html} Consumers}} page.
 
diff --git a/archiva-docs/src/site/apt/adminguide/upgrade.apt b/archiva-docs/src/site/apt/adminguide/upgrade.apt
index f1a664303..91be163c2 100644
--- a/archiva-docs/src/site/apt/adminguide/upgrade.apt
+++ b/archiva-docs/src/site/apt/adminguide/upgrade.apt
@@ -19,8 +19,10 @@ Upgrading Archiva
    Because of the changes in the search implementation starting in 1.2, a few additional steps need to be performed when upgrading Archiva from 1.1.x to
    1.2.x. Since the format of the index has changed in 1.2.x, the old index directory (which is located at <<</path/to/repo/.index>>> by default) needs to
    be removed. And in order for the artifacts in the repository to be indexed again, the last modified date of the artifacts need to be updated.
-   To do this, just execute <<find [REPOSITORY_DIRECTORY_NAME] | xargs touch>> at the base directory where the repository resides. Execute the repository
-   scanning so that the new index will be generated.
+   To do this, you can force Archiva to scan all the artifacts by ticking the 'Process All Artifacts' checkbox then clicking the 'Scan Repository Now' 
+   button in the Repositories page. Take note though that this feature is only available starting with version 1.2.3. Otherwise, you must execute
+   <<find [REPOSITORY_DIRECTORY_NAME] | xargs touch>> at the base directory where the repository resides and then force execute the repository scanning so
+   that the new index will be generated.
 
    In 1.2.2, the length of the specified fields in the database tables below were changed to 1020:
    
diff --git a/archiva-docs/src/site/resources/images/repositories.png b/archiva-docs/src/site/resources/images/repositories.png
new file mode 100644
index 000000000..5dc4679e8
--- /dev/null
+++ b/archiva-docs/src/site/resources/images/repositories.png
diff --git a/archiva-docs/src/site/resources/images/tour/admin.png b/archiva-docs/src/site/resources/images/tour/admin.png
index f77005d38..2fd4cc655 100644
--- a/archiva-docs/src/site/resources/images/tour/admin.png
+++ b/archiva-docs/src/site/resources/images/tour/admin.png