There is plenty of work done to create the collections (one at a time, in order) in order to perform a PUT request.
What dav server are you using when you got this error? The HTTP Response 500 is the likely culprit here. - Joakim Graham Leggett wrote: > Hi all, > > As a test I have configured the maven deploy:deploy-file goal to deploy to a > WebDAV server. The login and ssl part works fine, but the attempt to PUT > the file fails with a 403 response code (but not because of auth failure > according to the logs). > > It looks like the plugin is not making an attempt to create the > directories in the repository before trying to upload the file to the > repository, thus the failure: > > [Tue Jan 30 13:45:57 2007] [debug] mod_auth_ldap.c(382): [client > 172.18.132.82] > [7883] auth_ldap authenticate: accepting [EMAIL PROTECTED] > [Tue Jan 30 13:45:57 2007] [error] [client 172.18.132.82] Unable to PUT > new contents for /maven2/alchemy/test/0.0.0/test-0.0.0-win32.patch. [403, > #0] > [Tue Jan 30 13:45:57 2007] [error] [client 172.18.132.82] (2)No such file > or directory: An error occurred while opening a resource. [500, #0] > > Has anyone got the deploy:deploy-file target to work with DAV before? > > The command line is as follows, a "server" is defined correctly in > settings.xml: > > Graham-Leggetts-Computer:~ minfrin$ mvn deploy:deploy-file > -Dfile=subversion-package-fix.patch > -Durl=https://alchemy.scmb.co.za/maven2 -DrepositoryId=alchemy.scmb.co.za > -DgroupId=alchemy -Dversion=0.0.0 -Dclassifier=win32 -DartifactId=test > -Dpackaging=patch > > The [EMAIL PROTECTED] list suggested I try v1.0-beta-2 of wagon-webdav, but > this > has had no effect. > > Regards, > Graham > -- > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
