Return-Path: Delivered-To: apmail-archiva-dev-archive@www.apache.org Received: (qmail 2215 invoked from network); 17 Jun 2010 15:34:59 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 Jun 2010 15:34:59 -0000 Received: (qmail 38754 invoked by uid 500); 17 Jun 2010 15:34:59 -0000 Delivered-To: apmail-archiva-dev-archive@archiva.apache.org Received: (qmail 38695 invoked by uid 500); 17 Jun 2010 15:34:59 -0000 Mailing-List: contact dev-help@archiva.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@archiva.apache.org Delivered-To: mailing list dev@archiva.apache.org Received: (qmail 38686 invoked by uid 99); 17 Jun 2010 15:34:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jun 2010 15:34:58 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of wsmoak@gmail.com designates 209.85.161.42 as permitted sender) Received: from [209.85.161.42] (HELO mail-fx0-f42.google.com) (209.85.161.42) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jun 2010 15:34:51 +0000 Received: by fxm5 with SMTP id 5so37863fxm.15 for ; Thu, 17 Jun 2010 08:34:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=NBs7rhc0wUZwSib2IL7//WFTJMtqdYYd0/IQHjzSOF8=; b=uivTmfw5ge8UN+7nJDFuX7JSku4AwmQ1iwoOf4L/vG2FHFfaBclIKaRbTaDfp7ElQ9 ILfE65VwHFdRYbkpxBgGveKe7QRBFGs7zMlH0A+5tob7P5FbeceFiud+2UQUKsZl70er B0Klrvu8cRa2ydZtTTYXv6jSf8t6Bm8Tl7ik4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=MioekYDlzomXfNP9hFbhLyVQvQqlw14CYmCkcE1jw+xgZ+PZ9LyqfG9aEiVvZweQoh 8r8GWd9YZ/LXWC4cVqWKx8M5UXSNpR7hcHGKzZ/N6RCLdbU0fMr8mfU/gxgnVK7StlP1 j0krh3iNzevElOoJZAijENBExwPQfbwqhUex0= Received: by 10.239.182.67 with SMTP id p3mr713423hbg.47.1276788871098; Thu, 17 Jun 2010 08:34:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.239.172.79 with HTTP; Thu, 17 Jun 2010 08:34:11 -0700 (PDT) In-Reply-To: References: From: Wendy Smoak Date: Thu, 17 Jun 2010 11:34:11 -0400 Message-ID: Subject: Re: A few notes on new repository API To: dev@archiva.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Jun 17, 2010 at 10:29 AM, Deng Ching wrote: > For the staging repos in vmbuild, the location of the index is configured > outside of the repo so it doesn't get included when the repo is merged. > Currently, I don't think the path to the metadata repository can be > configured so it's always in the repo.. So it sounds like the merging feature needs to exclude the indexes and the metadata if they are found within the repository. Separately, would having two Archiva instances trying to update the metadata repository at the same time be problematic? Before with the database we would certainly have never tried pointing two instances at the same database... -- Wendy