svn commit: r680622 - /archiva/trunk/archiva-docs/src/site/apt/adminguide/standalone.apt

[oc...@apache.org]

Author: oching
Date: Mon Jul 28 21:15:19 2008
New Revision: 680622

URL: http://svn.apache.org/viewvc?rev=680622&view=rev
Log:
[MRM-888]
-updated the upgrade doc to include the necessary steps in order to use the search by java class/package/method

Modified:
    archiva/trunk/archiva-docs/src/site/apt/adminguide/standalone.apt

Modified: archiva/trunk/archiva-docs/src/site/apt/adminguide/standalone.apt
URL: http://svn.apache.org/viewvc/archiva/trunk/archiva-docs/src/site/apt/adminguide/standalone.apt?rev=680622&r1=680621&r2=680622&view=diff
==============================================================================
--- archiva/trunk/archiva-docs/src/site/apt/adminguide/standalone.apt (original)
+++ archiva/trunk/archiva-docs/src/site/apt/adminguide/standalone.apt Mon Jul 28 21:15:19 2008
@@ -155,14 +155,15 @@
 
 {Upgrading Archiva}
 
-   Upgrading Archiva is straightforward if the directions for separating the base from the installation above are followed. Simply retain the data directories (the repositories and database),
+   Upgrading Archiva is straightforward if the directions for separating the base from the installation above are followed. Simply retain the <<<data/repositories>>> and <<<data/databases/users>>> directories,
    and the configuration files (in the conf directory, or the other locations specified above) and use a new extracted installation of Archiva.
 
-   Note that the <<<users>>> database must always be retained as it contains the permissions and user information across versions. However, should it be necessary, the <<<archiva>>> database can
-   be removed at any time and re-created by scanning the repositories again.
+   Note that the <<<users>>> database must always be retained as it contains the permissions and user information across versions. However,
+   in order to take advantage of the improvements in search in Archiva 1.1, s.a. search by java class/package/method, the archiva database must
+   be re-created. So you need to delete the <<<data/databases/archiva>>> directory, delete the <<<.index>>> directories of your respective repositories, and execute the repository and database scanners after
+   starting Archiva.
 
-   The repository data is portable across versions, and multiple versions can be configured to look at the same repositories (though not run simultaneously). When scanned, an index is also created
-   in the root directory - while this shold remain portable across versions, it can also be removed and regenerated by scanning the given repository again from the web interface.
+   The repository data is portable across versions, and multiple versions can be configured to look at the same repositories (though not run simultaneously).