Here's a new one, wondering if anyone has seen this and sees the easy answer, while I research it.
I get this at the tagging phase... [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: No such revision 828262 If I rerun release:prepare some short time later... [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Path 'https://svn.apache.org/repos/asf/lucene/mahout/tags/mahout-0.2' does not exist in revision 828265 I've tried a rollback. On Thu, Oct 22, 2009 at 12:55 AM, Sean Owen <[email protected]> wrote: > It was either the <gpg.keyname>, or Jukka's suggestion to add the > apache-release profile. I get through key signing now. Thanks! I'll > update our wiki accordingly. > > Now crossing fingers that the rest goes smoothly... > > On Wed, Oct 21, 2009 at 11:20 PM, Benson Margulies > <[email protected]> wrote: >> Do you have the right stuff in your .m2/settings.xml? >> >> Here is the page I wrote for XmlSchema that might shed some light: >> >> When I do apache releases that are not targeted at Nexus, I use: >> >> <profile> >> <id>release</id> >> <properties> >> <gpg.passphrase>...my passphrase....</gpg.passphrase> >> <gpg.keyname>[email protected]</gpg.keyname> >> <deploy.altRepository>apache.releases::default::scp:// >> people.apache.org/home/bimargulies/public_html/maven_staging >> </deploy.altRepository> >> </properties> >> </profile> >> >
