The instructions here should also be applicable from 1.x to 1.3: http://archiva.apache.org/docs/1.3/adminguide/upgrade.html
Thanks, Deng On Fri, Feb 12, 2010 at 8:12 PM, Engebakken Geir <[email protected]>wrote: > Ok, thanks I will try that. Is upgrading straight forward, config kept etc > or is it raw overwrite so that we must reestablish what we have changed in > startup scripts/conf etc. > > > Geir > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Deng > Ching > Sent: 12. februar 2010 12:00 > To: [email protected] > Subject: Re: Problems browsing in Archiva > > Hi Geir, > > You might need to update the last modification date of the artifacts in > your > repository so that they get processed again. You can execute the following > command at the directory where the repo reside > > find [REPOSITORY_DIRECTORY_NAME] | xargs touch > > Make sure that you delete the .index file btw. > > I also suggest that you upgrade to the latest release (1.3), or if you > don't > want to upgrade to a major release, at least to 1.1.4 as it contains a > number of important fixes such as > http://jira.codehaus.org/browse/MRM-1152 :) > > Thanks, > Deng > > On Thu, Feb 11, 2010 at 7:36 PM, Engebakken Geir <[email protected] > >wrote: > > > Hi, > > > > we are still running archiva 1.1.1. > > > > We get an error when we try to browse for a specific .pom file in > archiva. > > When looking at the repositiory file system the pom is there, so I am > > suspecting some problems in the archiva database. A few days ago I had to > > remove an artifact, so I had to remove the archiva database and .index > file > > for one of our repositories as well. This error occurred after this so I > > suspect it might have something to do with that. > > > > I have also tried scanning the repos, but this seems to go very fast, too > > fast for it to be credible. Any suggestions on how to solve this? > > > > > > Geir > > > > > > >
