Hi, One of thus "fun" bugs...SlingWebDavServletTest recently started failing, it still worked at revision 1673619 of the launchpad/builder module, the error is "invalid workspace name sling-test".
I have fixed that in revision 1673619 but I'm wondering if the previous behavior was by design: That test was using URLs like http://localhost:8080/dav//sling-test/SlingWebDavServletTest1440776383506/test-io-handler-1 Note the // before sling-test. Until recently, Sling (or the Jackrabbit WebDAV libs, not sure where that happened) extracted an empty JCR workspace name from the //, which translates to the default JCR workspace and all is fine. Now if you use such an URL the parsing gets "sling-test" as the workspace name. Was that // handling by design, or was that a bug that was fixed recently? -Bertrand
