Thanks for the help Rémy. Although your suggestion wasn't the nature of our specific problem, I did end up getting this working after some more searching on Google. What is bothering me, though, is that I still don't know exactly why there was a problem in the first place. Here is what ended up working for me.
Background: My sources were initially checked out using using the subclipse plugin in eclipse. After I checked them out, I executed the 'mvn release:prepare' command, which was successful up to the point of creating the release tag as I have mentioned previously. Solution: After reading your response and doing some more searching on Google, I found http://64.233.167.104/search?q=cache:c-eapRRo1_gJ:docs.codehaus.org/display/MAVENUSER/MavenAndSourceforge+%2522issuer+is+not+trusted%2522+svn&hl=en&ct=clnk&cd=25&gl=us&client=safari this page on one of the codehaus wiki's. Their suggestion upon receiving the "Server certificate verification failed: issuer is not trusted" was to execute an 'svn log' command from the command line to force authentication with the webserver. Sure enough, when I did that, the svn command line client prompted me for my credentials and cached them. After that upon executing an 'mvn release:prepare' maven was able to resume the release and it was able to complete the tag operation. It seems as though the credentials that were cached by subclipse when I did the initial checkout of the sources were able to be used by maven when committing my release to the trunk, but not when doing the tag. Why this is the case, I don't know. Perhaps someone else can shed some light, but I've had to file this as a UFO (Unexplained Funny Occurrence) and move on. sigh. Thanks again for the help. -- Jason Rémy Sanlaville wrote: > > Hi Jason, > > Not sure, but if you can access to your svn repo with different URLs ( > https://www.<domain-ommitted>.com and http://www.<domain-ommitted>.com for > instance) it's possible that you made a checkout via one URL > (http://www.<domain-ommitted>.com > for instance) and maven-release-plugin try with another URL specify in the > scm section of your pom (https://www.<domain-ommitted>.com for instance). > > We had a such of problem with one of our project and maven-release-plugin > could also commit but not tag. > > I am not sure for the explanation but maven-release-plugin uses the svn > client install in your computer. > For the commit, it uses all the information in your .svn > For the tag, it seems that it indicates the URL of the tags (specify in > the > scm section of your pom) but in your .svn the URL is different and the > certificate is linked only with the checkout URL. > > HTH, > > Rémy > > -- 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#a13425936 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
