On 26/08/2009, at 7:30 PM, Deng Ching wrote:
After debugging this issue, the problem wasn't because of version
ranges but
because of the resource path determined. There is a check in the
webdav
component to only proxy metadata if the request has a default (Maven
2)
layout. It requires at least 3 occurrences of '/' in the path (e.g.
/eclipse/jdtcore/maven-metadata.xml). But in 1.2.2, the first '/'
was being
removed so the request path is now 'eclipse/jdtcore/maven-
metadata.xml'.
This would cause all requests with only three directory levels to
fail.
I'm canceling the release now, we need to fix this issue first..
(Thanks for catching this one Julien!)
Sorry, I think that was my fault. I found repeated inconsistencies
with that and tried to align them (and checked through the tests).
Seemed we were missing one.
I think that API needs to be cleaned up...
- Brett
