Subject says it all. Deployment fails PUTting to non-existent directories with HTTP 409. Is it correct that deploying to a WebDAV enabled Apache httpd can only be done by updating the local Maven installation adding support for WebDAV like
$ ls -lah lib/ext/ total 1492 drwxr-xr-x 2 schulte schulte 512B Aug 17 22:41 ./ drwxr-xr-x 3 schulte schulte 2.5K Sep 26 20:31 ../ -rw-r--r-- 1 schulte schulte 152B Aug 11 22:56 README.txt -rw-r--r-- 1 schulte schulte 29.4K Aug 17 22:41 commons-codec-1.2.jar -rw-r--r-- 1 schulte schulte 298K Aug 17 22:41 commons-httpclient-3.1.jar -rw-r--r-- 1 schulte schulte 318K Aug 17 22:41 jackrabbit-webdav-2.5.2.jar -rw-r--r-- 1 schulte schulte 16.9K Aug 17 22:41 jcl-over-slf4j-1.6.4.jar -rw-r--r-- 1 schulte schulte 33.1K Aug 17 22:41 wagon-webdav-jackrabbit-2.6.jar ? Deployment to OSSRH succeeds without having to add any WebDAV support and I would like to get rid of 'dav:http:' everywhere in favour of 'http:'. Is it Nexus behaving differently by creating missing directories ? Regards, -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
