This guide gives you some handy hints to upgrade from an archiva 1.0.x instance to a new version 1.1.x. It also describes where settings in archiva 1.0.x are stored in archiva 1.1.
Configuration Files
...
Description
...
Archiva 1.0.x settings
...
Archiva 1.1.x settings
x, which ones have to be kept, updated or removed.
How to Upgrade
See also: http://archiva.apache.org/docs/1.1.2/adminguide/standalone.html#Upgrading%20Archiva (replace 1.1.2 in that link with the version number you are upgrading to)
Warning |
---|
The following process kept all artifacts (as far as I can tell), but did not keep users for a 1.0.2 to 1.1.2 migration. |
Keep your repositories content ({{${archiva.base}/data/repositories/*) and delete the .index directories of your respective managed repositories (if they exist- see previous section), and execute the repository and database scanners after starting Archiva.
Here are the steps:
1. Compress the (old archiva version)/data dir and extract it into the {{
...
Patch for Needed for MRM-227 and the utf8 mysql "bug"
${archiva.base}/
...
data dir.
2. Delete the new {{${archiva.base}/data/archiva/database dir (that you copied)
3. Search for *.index directories under {{${archiva.base}/data and remove any you find. In *nix this can be done like:
Code Block |
---|
cd {{$\{archiva.base\}/data
find . -name "*.index"
(make sure it only finds those that you want to delete)
find . -name "*.index" -exec rm -rf {} \;
|
4. Go to archiva and click on these to execute the repository and database scanners (note: this may be overkill):
- Repository Scanning -> Update Consumers
- Database -> Update Cron
- Database -> Update Database Now
- Database -> Update Consumers (click on this under all sections)
- Repositories -> Scan Repository Now (click on this under all sections)
Archiva Settings
Archiva's configuration is loaded from the following files, in order of most precedent:
~/.m2/archiva.xml
...
${archiva.base}/apps/archiva/webapp/WEB-INF/classes/META-INF/plexus/application.xml
...
...
${archiva.base}/conf/
...
archiva.xml
conf/archiva.xml
...
- in the Archiva installation
It will be automatically updated.
Custom security settings
Didn't change between 1.0.x and 1.1.x : ${archiva.base}/conf/security.properties
Logs & Memory Settings
Description | Archiva 1.0.x settings | Archiva 1.1.x settings | ||
---|---|---|---|---|
JVM Settings |
|
| |
|
Wrapper logs | |
|
| |
Archiva Settings
Jetty logs | — | |
Requests logs | — | |
...
Jetty settings
Description | Archiva 1.0.x settings | Archiva 1.1.x settings |
---|---|---|
jetty server hostname & http port | | |
SMTP server settings
Description | Archiva 1.0.x settings | Archiva 1.1.x settings |
---|---|---|
SMTP server host, port & credentials | | |
Databases
Internal databases
Retain data/databases/users
directories and remove data/databases/archiva
.
External databases
If your are using some external databases like mysql.
...
Description | Archiva 1.0.x settings | Archiva 1.1.x settings |
---|---|---|
Put it in | | |
Datasources
Description | Archiva 1.0.x settings | Archiva 1.1.x settings |
---|---|---|
Datasources | | |
Instances
Archiva 1.0.x | Archiva 1.1.x |
---|---|
Archiva Database | To be truncated |
Archiva Users Database | To be kept |
Repositories
...
Standalone-specific
Scripts in ${archiva.base}/bin
Description | Archiva 1.0.x settings | Archiva 1.1.x settings |
---|---|---|
Start/Stop Script | | |
Miscellaneous
Description | Archiva 1.0.x settings | Archiva 1.1.x settings |
---|---|---|
Patch for Needed for MRM-227 and the utf8 mysql "bug" | | |
Issues
- Upgrading from v1.0.2 standalone to v1.1.2 standalone users were not kept (had to recreate)