This should later be resolved by running through both the repository scan and the database scan processes though?
On 05/02/2008, Heck, Joe <[EMAIL PROTECTED]> wrote: > That process (dropping in new directories to an archiva instance) is > exactly what I'm doing - works very nicely. One tidbit that I noticed in > version 1.0 is that if you have established an internal repository and > then add *to it* after the fact, the artifacts don't always get indexed > properly. > > I found that getting the directory in place prior to launching archiva > for the first time (I was shoving all my artifacts into the default > "internal" repository) worked to resolve that issue. > > -joe > > -----Original Message----- > Sent: Monday, February 04, 2008 9:15 AM > To: [EMAIL PROTECTED] > Subject: Re: Achiva and Proximity > > Sure - since both use repositories stored in the file system you can > configure Archiva to point at the disk location of the repositories > when you add managed repositories. They'll be scanned and indexed > after they are added. > > Archiva doesn't however have an option for importing configuration > from Proximity. > > Cheers, > Brett > > On 04/02/2008, SlinnHawkins, Jon (ELS-CAM) <[EMAIL PROTECTED]> > wrote: > > Hi All, > > > > Is it possible to migrate an existing Proximity repository to use > > Archiva ? > > > > Many thanks > > > > Jon > > > > > > > > This email is from Elsevier Limited, a company registered in England > and Wales with company number 1982084, > > whose registered office is The Boulevard, Langford Lane, Kidlington, > Oxford, OX5 1GB, United Kingdom. > > > > > > > -- > Brett Porter > Blog: http://www.devzuz.org/blogs/bporter/ > -- Brett Porter Blog: http://www.devzuz.org/blogs/bporter/
