So I was trying out maven 3.0.4, and it has problems when we have server elements(with username and password) defined in our settings, as we get a 403 because of the preemptive authentication(the credentials are valid and work for non-preemptive auth with maven 3.0.3). In this particular case its just for a GET request. I've tried turning preemptive auth off, but it didn't seem to work. Based on the info at: http://maven.apache.org/guides/mini/guide-http-settings.html Here is what I tried to turn it off: <servers> <server> <id>snapshots</id> <configuration> <wagonProvider>httpclient</wagonProvider> <httpConfiguration> <all> <params> <param> <name>http.authentication.preemptive</name> <value>%b,false</value> </param> </params> </all> </httpConfiguration> </configuration> <username>build</username> <password>...</password> </server> ...
I tried "get" instead of "all", but it still insists on preemptive auth(I'm using a packet sniffer to confirm). The message I'm seeing: [WARNING] Failure to transfer motive.smp:db:5.0.0.0-SNAPSHOT/maven-metadata.xml from http://maven.motive.com/content/groups/public-snapshots was cached in the local repository, resolution will not be reattempted until the update interval of snapshots has elapsed or updates are forced. Original error: Could not transfer metadata motive.smp:db:5.0.0.0-SNAPSHOT/maven-metadata.xml from/to snapshots (http://maven.motive.com/content/groups/public-snapshots): Access denied to: http://maven.motive.com/content/groups/public-snapshots/motive/smp/db/5.0.0.0-SNAPSHOT/maven-metadata.xml, ReasonPhrase:Forbidden. In this case it doesn't cause the build to fail, but in case my repository is clean it does. Does anyone have any clues about how to turn off preemptive auth for maven 3.0.4? The reason I'm even trying Maven 3.0.4, is in 3.0.3 I'm getting OutOfMemoryException on deploying large artifacts. It seems like its reading the whole artifact into memory. I was hoping with the wagon changes in 3.0.4 it might use a streaming approach instead. Thanks, Micah --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
