Is there documentation on doing this? I didn't see much in the way of upgrading aside from 1.0 to 1.1 and 1.1 to 1.2.
-----Original Message----- From: Brett Porter [mailto:[email protected]] On Behalf Of Brett Porter Sent: Wednesday, September 08, 2010 5:20 PM To: [email protected] Subject: Re: Upgrading from 1.1 If you're using the standalone bundle, I recommend following the steps to separate the configuration so that upgrades in future don't require copying the data around too. Cheers, Brett On 09/09/2010, at 4:00 AM, Shelley, Ryan wrote: > Just to follow-up, I have completed my upgrade from 1.1 to 1.3.1 without > problems. > > I shut down Archiva, backed up my data directory, removed the "archiva" > database directory, removed the ".index" directories in the repositories, > untarred the new archiva release, copied only the "archiva.xml" configuration > over, moved the data directory over, then restarted Archiva. After restart, > I re-ran the Repository Scans and Database Scan to rebuild the indexes and > clean things up. Maven builds seem to be running just fine against the new > version. > > Thanks for your input Wendy! > > -Ryan > > -----Original Message----- > From: Wendy Smoak [mailto:[email protected]] > Sent: Tuesday, September 07, 2010 6:04 PM > To: [email protected] > Subject: Re: Upgrading from 1.1 > > On Tue, Sep 7, 2010 at 8:39 PM, Shelley, Ryan <[email protected]> wrote: >> Would I have to re-configure everything after the upgrade? Repositories and >> Users, etc? > > No, that's stored elsewhere. There is a separate user database, don't > delete that one. The configuration is in archiva.xml in newer > versions. I'm not that familiar with 1.1 to be honest. > > The database has the info for the .../browse/... urls, which it can > re-construct when it scans all the poms. > > Now that I think of it, you'll probably want to delete the indexes > also (in the .index directory?) and let it rebuild those as well. > > -- > Wendy -- Brett Porter [email protected] http://brettporter.wordpress.com/
