I've been searching the groups, the web, and the doc and I've not been able
to find a solution to this.  Any help you can offer is much appreciated.

I have successfully executed half of a release:prepare.  The version numbers
in my all of my POMs were successfully updated and maven successfully
committed them to my scm repository.  We are using subversion over https. 
I've added the SSL certificate for the site to my keystore (at both the JVM
level and in a .keystore in my home directory).  I have also checked that
the fingerprint for the cert was added to 
~/.subversion/auth/svn.ssl.server.   The  release:prepare is failing with
this error when it attempts to create the tag for the release:

[INFO] [release:prepare]
[INFO] Resuming release from phase 'scm-tag'
[INFO] Tagging release with the label datamanager-1.0...
[INFO] Executing: svn --non-interactive copy --file
/tmp/maven-scm-2112306694.commit .
https://www.<domain-ommitted>.com/svn/tags/<dir-ommitted>/datamanager-1.0
[INFO] Working directory: /Users/jason/projects/DataManager-trunk
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: PROPFIND request failed on '/svn/tags/<dir-ommitted>/datamanager-1.0'
svn: PROPFIND of '/svn/tags/<dir-ommitted>/datamanager-1.0': Server
certificate verification failed: issuer is not trusted
(https://www.<domain-ommitted>.com)

Why would the commit to the same SCM succeed, while the tag operation fails
with this error?  I'm baffled.

Thanks for the help,
Jason
-- 
View this message in context: 
http://www.nabble.com/release%3Aprepare-failure-during-scm-tag-%3A---Server-certificate-verification-failed%3A-issuer-is-not-trusted-tf4678454s177.html#a13367420
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to