I made some more tests and I was wrong : relocation is still applied as expected.
http://localhost:8080/archiva/repository/maven/servletapi/jars/servletapi-2.4.jar <logs> 181281 [btpool0-4] DEBUG org.apache.maven.archiva.proxy.ProxyRequestHandler - Artifact requested is: servletapi:servletapi:jar:2.4:runtime 181297 [btpool0-4] DEBUG org.apache.maven.archiva.proxy.ProxyRequestHandler - Artifact servletapi:servletapi:2.4 has been relocated to javax.servlet:servlet-api:2.4 </logs> I then get a strange error : *Error 404 Not Found* Resource in error: http://localhost:8080/archiva/repository/servletapi/jars/servletapi-2.4.jar/servletapi/jars/servletapi-2.4.jar it.could.webdav.DAVException: Not found at it.could.webdav.methods.HEAD.process(HEAD.java:52) at it.could.webdav.methods.GET.process(GET.java:58) at it.could.webdav.DAVProcessor.process(DAVProcessor.java:79) at org.codehaus.plexus.webdav.simple.SimpleDavServerComponent.process(SimpleDavServerComponent.java:142) at org.apache.maven.archiva.web.repository.ProxiedDavServer.process(ProxiedDavServer.java:157) Seems the DAV server does not get the "relocated" path. 2007/2/7, nicolas de loof <[EMAIL PROTECTED]>:
This change has for side effect that archiva does not handle maven1 requests anymore : http://localhost:8080/archiva/repository/maven/activation/activation/1.0.2/activation-1.0.2.pom works as expected and will make a maven2 client relocate to javax.activation Previous archiva builds auto-detected maven1 formatted request and converted them to "Artifacts" internal object for resolution. A special case I contributed to was to handle relocation internally for such maven1 requests, as maven1 does not read those meta-data. now http://localhost:8080/archiva/repository/maven/activation/jars/activation-1.0.2.jaris 500 error: Could not find /activation/jars/activation- 1.0.2.jar in any of the repositories. This is a blocking regression for me as lot's of my projects still use maven1. 2007/2/7, Michael Horwitz < [EMAIL PROTECTED]>: > > Hi Nicolas, > > Suffered from exactly the same problem a few weeks back - turns out the > Archiva team have removed the proxy distinction. To access your > repository, > you simply go to the webdav URL (whatever the URL you set up for the > repository). This URL now provides all the proxy functionality (at least > as > far as I have tested it), and should work for Maven 1 requests as well. > You > do need to do some extra work to get everything working though: the > webdav > URL is secured, so by default will ask for a username and a password. To > > allow for anonymous access, you need to grant the guest user the > repository_observer role on all your repositories. > > Another little catch to look out for with Maven 1 and Archiva is > handling of > dependencies of type plugin - not sure if the bug has been fixed, but we > had > to apply a patch to get everything working. You should find the details > in > the Archiva bug tracking database, if not let me know and I can post > them up > here again. > > Mike. > > > On 2/7/07, nicolas de loof < [EMAIL PROTECTED]> wrote: > > > > Hello, > > > > I've installed archiva from a SVN checkout. I've configured a managed > > proxy > > and a proxied on to repo1.maven.org > > > > Requesting http://localhost:8080/archiva/repository > > /maven/activation/activation/1.0.2/activation- 1.0.2.pom works. > > > > Requesting http://localhost:8080/archiva/proxy > > /maven/activation/activation/1.0.2/activation-1.0.2.pom fails > > " > > HTTP ERROR: 404 > > > > There is no Action mapped for namespace / and action name proxy. Check > > if there is such an action name with such namespace defined in the > > xwork.xml and also if such an action class exists. Check also the log > > to see if the action class is successfully loaded. > > > > > RequestURI=/archiva/proxy/maven/activation/activation/1.0.2/activation- > > 1.0.2.pom > > Caused by: > > > > There is no Action mapped for namespace / and action name proxy. Check > > > if there is such an action name with such namespace defined in the > > xwork.xml and also if such an action class exists. Check also the log > > to see if the action class is successfully loaded. - [unknown > > location] > > at com.opensymphony.xwork.DefaultActionProxy.( > > DefaultActionProxy.java:72) > > at > > com.opensymphony.xwork.DefaultActionProxyFactory.createActionProxy( > > DefaultActionProxyFactory.java :46) > > ... > > " > > > > > > As I'm using archiva from maven1, I need the proxy feature to handle > > maven1-like requests : > > > > > > > http://localhost:8080/archiva/proxy/maven/activation/jars/activation-1.0.2.jar > > > > > > What's wrong with "/proxy" URI ? > > >
