Return-Path: Delivered-To: apmail-maven-archiva-dev-archive@locus.apache.org Received: (qmail 96172 invoked from network); 10 Oct 2007 09:50:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Oct 2007 09:50:51 -0000 Received: (qmail 72342 invoked by uid 500); 10 Oct 2007 09:50:37 -0000 Delivered-To: apmail-maven-archiva-dev-archive@maven.apache.org Received: (qmail 72229 invoked by uid 500); 10 Oct 2007 09:50:37 -0000 Mailing-List: contact archiva-dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: archiva-dev@maven.apache.org Delivered-To: mailing list archiva-dev@maven.apache.org Received: (qmail 72220 invoked by uid 99); 10 Oct 2007 09:50:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2007 02:50:36 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [69.36.241.87] (HELO mail.sventech.com) (69.36.241.87) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2007 09:50:38 +0000 Received: from mail.sventech.com (localhost.localdomain [127.0.0.1]) by mail.sventech.com (Postfix) with ESMTP id D0542480A2 for ; Wed, 10 Oct 2007 02:50:17 -0700 (PDT) Received: from [192.168.244.154] (ip72-208-63-32.ph.ph.cox.net [72.208.63.32]) by mail.sventech.com (Postfix) with ESMTP id A0F284809D for ; Wed, 10 Oct 2007 02:50:17 -0700 (PDT) Message-ID: <470CA07B.5030605@erdfelt.com> Date: Wed, 10 Oct 2007 02:50:51 -0700 From: Joakim Erdfelt User-Agent: Thunderbird 2.0.0.0 (X11/20070501) MIME-Version: 1.0 To: archiva-dev@maven.apache.org Subject: Re: [Proposal] Repository Layout Detection/Interaction Changes. References: <4706B3A3.5090501@apache.org> <4EC61156-4AC1-4A87-8665-E3168B0E5E9A@apache.org> <470B906B.2040106@erdfelt.com> <4c39e3030710090825y64ddc76fyeb0b5d428ca403fb@mail.gmail.com> <1E544674-B375-4F8D-A1A7-69FD2E2C249B@apache.org> <4c39e3030710092220r5804796fh458cebe2a388013a@mail.gmail.com> <7CBE8591-EAE6-4757-93A4-11637AEA1539@apache.org> In-Reply-To: <7CBE8591-EAE6-4757-93A4-11637AEA1539@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-Virus-Checked: Checked by ClamAV on apache.org It works! yay! And there was much rejoicing... nicolas, Check out the new RepositoryRequest object, and ManagedRepositoryContent structure inside of archiva-repository-layer. There's plenty of unit tests to show that they work. Its late for me, I'm going to get some sleep and expand on this (or reply to all of Brett's questions) when I get up. - Joakim Brett Porter wrote: > Joakim seems to be indicating he'll finish something already today, so > we should probably take a look at that and go from there. > > - Brett > > On 10/10/2007, at 7:20 AM, nicolas de loof wrote: > >> I'd suggest a "merge" of 2 options : >> >> 1 . have an exception list, used by the LegacyBidirectionalLayout to >> resolve >> those artifactIds, maybe stored in the archiva DB or in a file (I've >> never >> used jpox, so can't say if it's simple to do) >> >> 2 . add an optional ArtifactReferenceVerifier as param of >> toArtifactReference(path) : >> >> public interface ArtifactReferenceVerifier >> { >> boolean isValidReference( ArtifactReference ref ); >> } >> >> 3 . make the BidirectionalLegacyLayout build the default >> [artifactId:version:classifier] and check for validity. If not, build >> all >> possible combinations and test them until getting a valid one. Store the >> result in exceptions (cache). >> >> 4 . From the DavProxyServlet, pass a verifier that check for the file to >> exists in any proxied repo. >> In other place, pass null. The artifact used is allready in the >> managed repo >> so is allready registered as an exception if required. >> >> Using this, we can provide a default exception list for known issues >> from >> central, and also provide with fiew changes a deterministic >> LegacyBidirectionalLayout with auto-enhancement of the exception list. >> >> Nico. >> >> >> >> >> 2007/10/9, Brett Porter : >>> >>> Hi Nicolas, >>> >>> Thanks for the summary - it sounds spot on. Just one clarification: >>> >>> On 09/10/2007, at 5:25 PM, nicolas de loof wrote: >>> >>>> Brett suggest to have a dedicated UI to maintain a set of >>>> exceptions. That >>>> would be a way to force the LegacyBidirectionalLayout to be >>>> deterministic. >>>> This option has less impact on archiva design, but requires >>>> - a new web UI >>>> - some work for the repository manager >>> >>> I actually suggested the simplest possible route here - I think if >>> these can be handled via a configuration file that is enough as we >>> shoul be able to pre-specify the vast majority of the exceptions >>> based on the rules for central. >>> >>> What is your opinion on the best way forward? >>> >>> Thanks, >>> Brett >>> >>> -- >>> Brett Porter - brett@apache.org >>> Blog: http://www.devzuz.org/blogs/bporter/ >>> > > -- > Brett Porter - brett@apache.org > Blog: http://www.devzuz.org/blogs/bporter/ > -- - Joakim Erdfelt joakim@erdfelt.com Open Source Software (OSS) Developer