Karl, I need your help. The deployment within release:perform failed due to
credentials:

[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
on project maven-shared-utils: Failed to deploy
 artifacts: Could not transfer artifact
org.apache.maven.shared:maven-shared-utils:jar:0.8 from/to
apache.releases.https (https://repository.apache.org/service/
local/staging/deploy/maven2): peer not authenticated

I am still using the same password in Ldap and still the same settings.xml
as I release surefire:2.18.1 in December. Other things work like connection
to minotaur.

This is my server settings.xml:

                <server>
                  <id>apache.snapshots.https</id>
                  <username>tibordigana</username>
                  <password>***</password>
                </server>
                <server>
                  <id>apache.website</id>
                  <username>tibordigana</username>
                  <password>***</password>
                  <filePermissions>664</filePermissions>
                  <directoryPermissions>775</directoryPermissions>
                </server>
                <server>
                  <id>apache.releases.https</id>
                  <username>tibordigana</username>
                  <password>***</password>
                </server>
                <server>
                  <id>stagingSite</id> 
                  <username>tibordigana</username>
                  <password>***</password>
                  <filePermissions>664</filePermissions>
                  <directoryPermissions>775</directoryPermissions>
                </server>

Any ideas?



--
View this message in context: 
http://maven.40175.n5.nabble.com/Release-of-maven-shared-utils-0-8-and-maven-verifier-1-6-tp5836620p5837694.html
Sent from the Maven Developers mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to