Thanks for the info Graham. That does make some sense. However, do you have any ideas why the maven release plugin would be able to execute the commit of the release POMs to the trunk prior to tagging? I can't figure that one out, unless I've somehow misinterpreted the sequence of events that lead up to this problem.
Best regards, Jason Graham Leggett wrote: > > On Fri, October 26, 2007 2:16 pm, Jason Mihalick wrote: > >> 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. > > Subclipse (to my knowledge), uses a pure Java implementation of subversion > in order to work. As I understand it, this pure Java client[1] has its own > mechanism to handling credentials. > > Maven's scm handling calls the svn binary directly, which then uses a > different mechanism for caching credentials. I suspect this is why your > behaviour in subclipse doesn't follow on from the behaviour of the svn > client. > > [1] The pure Java svn client was written to solve the painful issue of > having to fiddle around with platform specific issues when trying to > execute the svn native binary. > > Regards, > Graham > -- > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- 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#a13428128 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
