Author: oching
Date: Thu Jan 28 10:10:27 2010
New Revision: 904024

URL: http://svn.apache.org/viewvc?rev=904024&view=rev
Log:
[MRM-1320] Incorrect Archiva version specified for the "Process All Artifacts" 
feature in upgrade docs 
merged from trunk -r904015

Modified:
    
archiva/branches/archiva-1.3.x/archiva-docs/src/site/apt/adminguide/upgrade.apt

Modified: 
archiva/branches/archiva-1.3.x/archiva-docs/src/site/apt/adminguide/upgrade.apt
URL: 
http://svn.apache.org/viewvc/archiva/branches/archiva-1.3.x/archiva-docs/src/site/apt/adminguide/upgrade.apt?rev=904024&r1=904023&r2=904024&view=diff
==============================================================================
--- 
archiva/branches/archiva-1.3.x/archiva-docs/src/site/apt/adminguide/upgrade.apt 
(original)
+++ 
archiva/branches/archiva-1.3.x/archiva-docs/src/site/apt/adminguide/upgrade.apt 
Thu Jan 28 10:10:27 2010
@@ -19,8 +19,8 @@
    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, 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
+   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.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.
 


Reply via email to