The following comment has been added to this issue:

     Author: Ben Walding
    Created: Sat, 20 Mar 2004 9:20 AM
       Body:
Nah, at this point I'm not convinced wagon is relevant.

Wagon requires that you know the repo layout - something that is not fixed and is 
subject to change.  


All that maven-proxy requires is that you know the SNAPSHOT identifier.

Converting http-500 errors to http-404 is trivial once I get into gear on it.
---------------------------------------------------------------------
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENPROXY-1&page=comments#action_17740

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVENPROXY-1

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVENPROXY-1
    Summary: maven-proxy should handle missing files gracefully
       Type: New Feature

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-component-proxy

   Assignee: 
   Reporter: Trygve Laugst?l

    Created: Wed, 8 Oct 2003 4:02 PM
    Updated: Sat, 20 Mar 2004 9:20 AM

Description:
Now a 500 jetty error page is returned:

HTTP ERROR: 500 file:/tmp/trygvela/maven-proxy//foobar
RequestURI=/foobar 


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to