Brett Porter wrote:
On 17/04/2009, at 6:19 PM, Todor Boev wrote:
There are no new databases. Also there are no new new files in the
archiva-1.2 directory, nor in the /var/archiva directory.. I noticed
however that there are two databases archiva_users and
apache_archiva, which seem to contain *identical* lists of tables (28
tables in each). By the prefixes of the table names I would expect
that archiva_users should contain only SECUTIRY_XXXX tables while
apache_archiva should contain everything else.
That's right. You might need to double check that you don't have a
typo in jetty.xml that is being used then.
- Brett
I'm thinking I should backup the databases and than try to drop all
tables in apache_archiva and retain only the SECURITY tables in
archiva_users? This seems to confirm to the migration guide:
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 (and higher
versions), 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.
I suppose this is tailored for Derby. The analog in my case would be to
drop everything in apache_archiva and retain only the SECURITY_XXX
tables from archiva_users right?
-Todor
