>From a more general perspective, I would say it looks like the direct browsing 
>functionality has inappropriately mixed filesystem traversal logic with 
>database traversal logic.  (When I say 'direct browsing' I mean via the 
>/archiva/repository URL).   In other words, it looks like it is using 
>filesystem awareness to list the leaf contents of a node, but then validate 
>the leaf elements against the database.   Why not just traverse the nodes in 
>the database, display only what is indexed.   Then look at the indexing layer 
>to tackle the question of what is valid to be indexed.  And make me happy by 
>making the layout format a user-configurable option, including "unrestricted". 
> :)   Let Maven enforce the rigid Maven-specific assumptions, then maybe 
>Archiva can expand its value proposition larger than just the subset of Maven 
>users.

> -----Original Message-----
> From: Joakim Erdfelt [mailto:[EMAIL PROTECTED] 
> Sent: Friday, March 07, 2008 9:19 PM
> To: archiva-users@maven.apache.org
> Subject: Re: Any way to ignore LayoutExceptions?
> 
> How about we do this ...
> 
> 1) Attempt to detect layout
> 1a) Is it default layout?
>   Translate to repository layout structure and return resource.
> 1b) Is it legacy layout?
>   Translate to repository layout structure and return resource.
> 2) Does resource exist as-is?
>     Return resource.
> 3) Fail
> 
> ?
> 
> Step 2 would be new.
> What sort of failure (other than 404) would be appropriate in Step 3?
> 
> - Joakim
> 
> Brett Porter wrote:
> > Yes - I agree.
> >
> > On 08/03/2008, Brown, Carlton <[EMAIL PROTECTED]> wrote:
> >   
> >> I could be naïve but in my mind, if you're providing an 
> interface to browse a directory structure, each displayed 
> element should be accessible.  It's weird when directory 
> contents (like jar files) are displayed, but the interface 
> throws layout exceptions when they're clicked on.
> >>
> >>
> >>  > -----Original Message-----
> >>  > From: Brett Porter [mailto:[EMAIL PROTECTED]  > Sent: 
> >> Friday, March 07, 2008 12:20 AM  > To: 
> archiva-users@maven.apache.org  
> >> > Subject: Re: Any way to ignore LayoutExceptions?
> >>  >
> >>  > If you believe the format is actually valid, it's a 
> bug. Some  > 
> >> of these have been fixed for 1.0.2 - you might like to check JIRa.
> >>  >
> >>  > - Brett
> >>  >
> >>  > On 07/03/2008, Brown, Carlton 
> <[EMAIL PROTECTED]> wrote:
> >>  > > I've deployed an artifact that does not have the same name as 
> >> its  > > parent  module (long story) and I can't retrieve it,  > 
> >> getting this exception:
> >>  > >
> >>  > org.apache.maven.archiva.repository.layout.LayoutException: 
> >> Invalid  > > path  to Artifact: filename format is invalid, should 
> >> start with  > > artifactId as  stated in path.
> >>  > >  Is there any way I can prevent Archiva from 
> enforcing this  > 
> >> restriction?
> >>  > >
> >>  > >  Thanks,
> >>  > >  Carlton
> >>  > >
> >>  > >
> >>  > >
> >>  > >  -----------------------------------------
> >>  > >  ====================================================
> >>  > >  This message contains PRIVILEGED and CONFIDENTIAL  > 
> >> information that  > > is intended only for use by the  named 
> >> recipient. If you  > are not the  > > named recipient,  any 
> >> disclosure, dissemination, or action  > based on  > > the 
> contents of 
> >> this message is prohibited. In such  case please  > > 
> notify us and 
> >> destroy and delete all  copies of this transmission.
> >>  > > Thank you.
> >>  > >  ====================================================
> >>  >
> >>  >
> >>  > --
> >>  > Brett Porter
> >>  > Blog: http://blogs.exist.com/bporter/  >
> >>
> >>     
> >
> >
> >   
> 
> 

Reply via email to