I believe Archiva will handle a local repository directly since it
uses the same format for tracking remote metadata file downloads,
which is the main difference. If you have artifacts in the local
repository that were generated with 'mvn install' you may get into
trouble - removing versions that are -SNAPSHOT (not timestamped) and
their associated metadata files (which will contain
<useLocalCopy>true</>) will cover these.
- Brett
On 27/05/2009, at 4:56 AM, Wendy Smoak wrote:
> On Tue, May 26, 2009 at 12:17 AM, James Barrow
> <
james.barrow@...> wrote:
>
>> Thanks for the reply Wendy, I did try that, but it unfortunately
>> doesn't
>> work. Due to bandwidth constraints, I really wouldn't want to re-
>> download
>> everything from the central repo, also, because there's so many
>> artifacts,
>> manually uploading everything to Archiva would take so long.
>>
>> Hopefully they add this functionality.
>
> I'm pretty sure someone has written a script to convert a local repo
> into a remote one-- check the Maven users list archives.
>
> --
> Wendy
