Thanks!

Here was my experience with the upgrade:

* I noticed that instead of having to go into the platform specific dir under bin/ that there were new archiva and archiva.bat scripts that handled stop/stop etc. * I noticed the port settings now need to be done in jetty.xml instead of plexus.xml (that is a bit diff than the wiki page). * The admin user got removed/didn't make the transition (even though I had compressed and exploded the whole data dir and did what I said below, so users dir was there). So I just recreated the admin user. :(

According to the instructions you only need to "execute the repository and database scanners", but I was a bit unsure what that meant exactly (at least for the database stuff), so I did all of this:
* 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)

The slowness went away when building via maven 2 which was the main thing I was trying to fix (yay!).

I don't know if that is because some dependence on an external repo that was down/slow was fixed or if it was the upgrade though (more likely the former than the latter I suppose).

Thanks!

Gary


Arnaud HERITIER wrote:
If you customized your settings you can have a look at this page :
http://cwiki.apache.org/confluence/display/ARCHIVA/Upgrading+from+1.0.x+to+1.1.x

Arnaud

On Mon, Sep 29, 2008 at 6:30 PM, Gary Weaver <[EMAIL PROTECTED]> wrote:

Hey everyone,

Our internal archiva v1.0.2 instance was being extremely slow this morning
for some reason (so maven 2 builds were slow), so I thought I might upgrade
to the latest version to see if it would help.

After a little while searching I found some info at the bottom of:

http://archiva.apache.org/docs/1.1.2/adminguide/standalone.html#Upgrading%20Archiva
about upgrading Archiva.

I tar/gzipped the (standalone) apache-archiva-1.0.2 dir>/data dir and
extracted it into the new/never started (standalone) apache-archiva-1.1.2
dir (which didn't already have a data dir).

Did my best to follow directions by deleting the
apache-archiva-1.1.2/data/archiva/database directory and then searched for
*.index directories under apache-archiva-1.1.2/data, but didn't find any to
remove.

Is there anything else I need to do?

Thanks in advance,

--
Gary Weaver
Application and Database Services
Office of Information Technology
Duke University






--
Gary Weaver
Application and Database Services
Office of Information Technology
Duke University

Reply via email to