I have the same error. I successfully uploaded a jar on a managed repository : http://forge.octo.com/archiva/browse/formview/formview/1.0-b5
But If I try to access it with a m2 layout : http://forge.octo.com/archiva/repository/3rd-party/formview/jars/formview-1.0-b5.jar=> it.could.webdav.DAVException http://forge.octo.com/archiva/proxy/3rd-party/formview/jars/formview-1.0-b5.jar=> 404 (normal, it's not a proxy) a m1 layout : http://forge.octo.com/archiva/proxy/3rd-party/formview/formview/1.0-b5/formview-1.0-b5.jar=> 404 (normal, it's not a proxy) http://forge.octo.com/archiva/repository/3rd-party/formview/formview/1.0-b5/formview-1.0-b5.jar=> OK Any idea ? Arnaud On 11/13/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 11/12/06, Brett Porter <[EMAIL PROTECTED]> wrote: > Does the directory you configured already exist? I don't think > Archiva creates it at present. > > This isn't anything to do with Jetty - we use the could.it webdav > library (as you can see through the trace, it comes from a > RepositoryAccess servlet in our code). The directory did not exist, but I get the same error if I create a managed repository pointed at my local m2 repo. Creating target/my-managed-repository also didn't help. Somehow I managed to provoke the following error once, which sounds more like what you're talking about. I haven't been able to make it happen again. HTTP ERROR: 500 Root "E:\svn\maven\archiva\archiva-webapp\target\my-managed-repository" is not a directory RequestURI=/repository/MyRepo Caused by: java.io.IOException: Root "E:\svn\maven\archiva\archiva-webapp\target\my-managed-repository" is not a directory -- Wendy
