I'm not sure how <snapshotRepository> impacts no credentials available -- but it is not a snapshot, <version>16</version> from the POM, packaging is <packaging>pom</packaging> as this would be the simplest use-case. Again, based on the Debug:
[DEBUG] not adding permissions to wagon connection Not sure what to do.... -D > -----Original Message----- > From: Carlos Sanchez [mailto:[EMAIL PROTECTED] > Sent: Monday, June 12, 2006 12:18 PM > To: Maven Users List > Subject: Re: Wagon-webdav distribution - where to put > username/password > > are you trying to deploy a snapshot? if so <repository> > doesn't apply, <snapshotRepository> does > > Paste your pom else > > On 6/12/06, Darren Hartford <[EMAIL PROTECTED]> wrote: > > I must be ignorant, I am following that example, have settings in > > settings.xml, using wagon-webdav-1.0-beta-1-SNAPSHOT from > Subversion > > today (6/12/2006), and still unable to authenticate (with a known > > username/password that is tested on the WebDAV site that works fine > > with other tools, as well as manually with full PUT/MKCOL > permissions). > > > > Maven Debug Output: > > ============= > > [DEBUG] -- end configuration -- > > [INFO] deploy:deploy > > WAGON_VERSION: 1.0-beta-1-SNAPSHOT > > [DEBUG] not adding permissions to wagon connection Jun 12, 2006 > > 11:41:14 AM org.apache.commons.httpclient.HttpMethodBase > > processAuthenticationResponse > > WARNING: No credentials available for the 'my webdav secure realm' > > authentication realm at myserver > > ...... > > Caused by: org.apache.maven.wagon.TransferFailedException: > Failed to > > transfer file: http://myserver/repo/myfile. Return code is: 401 > > Unauthorized > > at > > > org.apache.maven.wagon.providers.webdav.WebDavWagon.put(WebDavWagon.ja > > va > > :280) > > at > > > org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(De > > fa > > ultWagonManager.java:180) > > at > > > org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(Defa > > ul > > tWagonManager.java:109) > > at > > > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defa > > ul > > tArtifactDeployer.java:77) > > ... 11 more > > ============= > > > > What else should I test? When authentication is disabled on > the WebDAV > > server, everything works fine. I tried changing the ID in > settings.xml > > to be 'my webdav secure realm', but that didn't work either. > > > > Note above: "[DEBUG] not adding permissions to wagon connection" > > > > -D > > > > > > > -----Original Message----- > > > From: Carlos Sanchez [mailto:[EMAIL PROTECTED] > > > Sent: Monday, June 12, 2006 8:36 AM > > > To: Maven Users List > > > Subject: Re: Wagon-webdav distribution - where to put > > > username/password > > > > > > Yes, > > > http://maven.apache.org/guides/mini/guide-deployment-security- > > > settings.html > > > > > > > On 6/7/06, Darren Hartford <[EMAIL PROTECTED]> wrote: > > > > > Hey all, > > > > > I'm trying to distribute artifacts to a webdav > server, but I do > > > > > not seem to know where to put the username/password. > When the > > > > > webdav server (apache 2.2) is un-secured, it works fine. > > > > > > > > > > Configured Maven as follows: > > > > > > > > > > Pom.xml > > > > > ========================= > > > > > <distributionManagement> > > > > > <repository> > > > > > <id>my-secure-repo</id> > > > > > <url>dav:http://reposerver/myrepo</url> > > > > > ... > > > > > ========================== > > > > > > > > > > Then tried settings.xml > > > > > ====================== > > > > > <servers> > > > > > <server> > > > > > <id>my-secure-repo</id> > > > > > <username>userthingy</username> > > > > > <password>passwordthingy</password> > > > > > ...... > > > > > ====================== > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > I could give you my word as a Spaniard. > No good. I've known too many Spaniards. > -- The Princess Bride > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
