Wagon creates directory, but for WEB-DAV protocol. It doesn't create directories for wagon-http-lightweight protocol (AFAIK this protocol doesn't support creating directories at all).
The problem is the wagon by default binds https://... to this wagon-http-lightweight, but not to web-dav. To make the thinks worse webdav://... also does not work for me in release plugin. Thank you, Piotr Tabor Carlos Sanchez pisze: > check the permissions because wagon definitely creates the dirs > > On 9/6/07, Rémy Sanlaville <[EMAIL PROTECTED]> wrote: > >> Hi Michael, >> >> Sorry for my late reply, but I am quite busy at the moment... >> >> 2007/9/1, Michael McCallum <[EMAIL PROTECTED]>: >> >>> cat /etc/debian_version >>> lenny/sid >>> >>> enabled dav and dav_fs >>> if you need auth - i recommend - >>> using digest authentication >>> >>> <Directory /path/to/repo> >>> Dav on >>> </Directory> >>> >>> thats all nothing magic >>> >> It seems that our apache configuration is ok (cf. our configuration at the >> end). >> >> are you using ssl? if you you need to ensure that the vm running maven >> >>> trusts >>> the certificate >>> >> Not for the moment. >> >> We continue some tests this morning and it seems effectively that >> wagon-webdav do not ask for the creation of the directories before uploading >> the artifact as we can see in the following logs : >> >> [Thu Sep 06 10:36:27 2007] [error] [client 10.194.3.100] Unable to PUT >> new contents for >> /inhouse.snapshot/com/test/my-plugin/1.0-SNAPSHOT/my- >> plugin-1.0-20070906.083623-1.jar. >> [403, #0] >> [Thu Sep 06 10:36:27 2007] [error] [client 10.194.3.100] (2)No such file >> or directory: An error occurred while opening a >> resource. [500, #0] [Thu Sep 06 10:38:55 2007] [error] [client >> 10.194.3.100] File does not >> exist: /home/maven2/proximity/inhouse.snapshot/storage/com >> >> If I create the com directory then I have the same error log for the next >> directory: test >> >> [Thu Sep 06 10:36:27 2007] [error] [client 10.194.3.100] Unable to PUT >> new contents for >> /inhouse.snapshot/com/test/my-plugin/1.0-SNAPSHOT/my- >> plugin-1.0-20070906.083623-1.jar. >> [403, #0] >> [Thu Sep 06 10:36:27 2007] [error] [client 10.194.3.100] (2)No such file >> or directory: An error occurred while opening a >> resource. [500, #0] [Thu Sep 06 10:38:55 2007] [error] [client >> 10.194.3.100] File does not >> exist: /home/maven2/proximity/inhouse.snapshot/storage/com/test >> >> Here is my configuration: >> - apache version: >> ii apache2-mpm-itk 2.2.3-01-1+b7 multiuser >> MPM for Apache 2.2 >> ii apache2.2-common 2.2.3-4+etch1 Next >> generation, scalable, extendable web server >> >> - apache conf: >> >> NameVirtualHost *:80 >> <AuthnProviderAlias ldap ldap-alias1> >> AuthLDAPURL >> ldap://gdc1.mydomain.fr:389/OU=Annuaire,DC=rd,DC=mydomain,DC=fr?sAMAccountName?base?(objectClass=user) >> </AuthnProviderAlias> >> >> <VirtualHost *:80> >> ServerName gmaven2.mydomain.fr >> DocumentRoot /home/maven2/proximity >> SuexecUserGroup tomcat55 www-data >> >> Alias /inhouse /home/maven2/proximity/inhouse/storage >> Alias /inhouse.snapshot /home/maven2/proximity/inhouse.snapshot/storage >> >> DavLockDB /var/lock/dav/DavLock >> >> <Directory "/home/maven2/proximity"> >> Options Indexes FollowSymLinks MultiViews ExecCGI >> AllowOverride None >> Order allow,deny >> allow from all >> AuthType Basic >> AuthBasicProvider file ldap-alias1 >> AuthName LDAP_Protected_Place >> AuthzLDAPAuthoritative off >> AuthUserFile /var/lib/misc/htpasswd >> Require valid-user >> DAV On >> </Directory> >> </VirtualHost> >> >> I use the 1.0-beta-2 version of wagon-webdav. >> <extensions> >> <extension> >> <groupId>org.apache.maven.wagon</groupId> >> <artifactId>wagon-webdav</artifactId> >> <version>1.0-beta-2</version> >> </extension> >> </extensions> >> >> Thanks, >> >> Rémy >> >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
