Hi, The [auth] section in .hgrc is quite new -- it looks like it was added just a week ago, in http://www.selenic.com/repo/index.cgi/hg/rev/89c80c3dc584 -- so it's most likely that your version of mercurial does not support it yet. With that section not available, the correct method is to embed the password in the push url in the paths section of the hgrc, as you have done. It's possible that MercurialEclipse simply doesn't handle such URLs correctly. As a shot in the dark, maybe it doesn't use % as an escape, and thus simply "%40" rather than "%%40" would work, but I don't have eclipse easily accessible to test this out.
I'd suggest some combination of the following: - try a bleeding-edge hg that supports the auth section - ask the MercurialEclipse authors / user list - ask on the hg mailing list at http://selenic.com/mailman/listinfo/mercurial -- Jacob Lee [email protected] 2009/5/12 Stephan Mühlstrasser <[email protected]>: > > Hi, > > I'm participating in the Mercurial beta program (the project is at > http://clojure-dev.googlecode.com/hg/), and I have a question > regarding recommendations for automatic authentication. I'm using > Mercurial 1.1.2 on Ubuntu 8.10 together with the MercurialEclipse > plugin 1.3.1019. > > The cloning instructions tell the following for pushing changes > (assuming "[email protected]" as my Google account name): > > # Project members authenticate over HTTPS to allow pushing changes. > hg push https://[email protected]@clojure-dev.googlecode.com/hg/ > > When prompted, enter your generated googlecode.com password. > > This certainly works, but as I would like to be able to push without > having to enter my password, I tweaked the .hg/hgrc file of a clone > like this (assuming that "password" is my generated googlecode.com > password): > > [paths] > default = > https://my.address%%40something.com:[email protected]/hg/ > > This allows to run "hg push" without having to enter the password > interactively. > > The problem is that this method does not work with the > MercurialEclipse plugin. It seems to mess up the URL when attempting > to push the changes. > > In order to avoid the problematic URL that contains username and > password I try to work around this by using the [auth] section in the > hgrc file (see http://www.selenic.com/mercurial/hgrc.5.html), like > this: > > [auth] > clojuredev.prefix = clojure-dev.googlecode.com/hg/ > clojuredev.username = [email protected] > clojuredev.password = password > clojuredev.schemes = https > > [paths] > default = https://clojure-dev.googlecode.com/hg/ > > But this seems to have no effect. When executing "hg push" from the > command line I'm prompted for username and password. > > So finally my question: Should the Mercurial authentication via the > [auth] section work with googlecode.com? Or am I misunderstanding the > purpose of the [auth] section? > > Sorry if I'm barking up the wrong tree here, but I currently have no > other remote Mercurial repository where I could try this for a > comparison. > > Thanks > Stephan > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
