Apache
/
archiva
mirror of https://github.com/apache/archiva.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[MRM-1320] Incorrect Archiva version specified for the "Process All Artifacts" feature in upgrade docs 

o update reference to version 1.2.3 to 1.3 instead


git-svn-id: https://svn.apache.org/repos/asf/archiva/trunk@904015 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Maria Odea B. Ching 2010-01-28 09:42:53 +00:00
parent f90bb19efe
commit b3440e6d18
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
archiva-docs/src/site/apt/adminguide/upgrade.apt
View File

@ -19,8 +19,8 @@ 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 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 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. 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' 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 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 <<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. that the new index will be generated.