Upgrading Archiva is straightforward, particularly if the directions for separating the base from the installation are followed. You need to retain the following directories:
The following describes instructions specific to upgrading between different versions.
All Java packages have changed from org.apache.maven.archiva to org.apache.archiva and have undergone significant changes. If you have written custom consumers, are using the XML-RPC client, or interfacing with other Java libraries the code will need to be adjusted.
If you had used the undocumented ability to modify application.xml to alter the configuration search path, note that in Archiva 1.4+ you must use the org.apache.archiva configuration search path instead of org.apache.maven.archiva.
If you are using the Jetty standalone configuration with a custom jetty.xml, note that it has been upgraded to Jetty 7 as of Archiva 1.4-M2. You will need to recreate your customisations using the jetty.xml shipped with Archiva.
In addition, you now need to ensure that a temp directory is created inside the Archiva application base directory (alongside conf, data and logs).
Since Archiva 1.2.2, the Jetty version has been upgraded to 6.1.19. If upgrading to Archiva 1.2.2 (or higher versions), there is a need to update the library contents listed in ARCHIVA_BASE/conf/wrapper.conf with the ones included in the new distribution if the ARCHIVA_BASE directory is separate from the installation.