Also, I forgot to tell you that you can reset the default repository via MercurialEclipse, by going to the properties of your project > Mercurial. You can use the **Set as default** dropdown list, which contains all repositories either known to MercurialEclipse or referenced in .hg/hgrc files.
Again, the only thing to worry about is the password (when the URL to the repository contains user credentials). Thank you for your question, I've added it to the list of many things about which I want to write Wiki entries. 2017-05-16 9:47 GMT+02:00 Amenel Voglozin <[email protected]>: > Hi Jay, > > Repos are indeed listed twice in the prefs file. Here is some information > (from my maintenance note file) about the contents of that file relative to > repositories: > > * The list of known repositories is stored with the key `repo_` > * The current default repository of a project is stored with the key (only > one value) `def_repo_repo_<project path>` > * The association between a project and a repo is stored with the key (one > or many values) `repo_<project path>`. These repositories are shown at the > top of the repo list in the **Team** > **Synchronize With** wizard (this > wizard is what you refer to as "the pop-up inthe dialog"). > > In your case, you can edit or delete the line that starts with > `def_repo_repo_` but be aware (if you chose to delete instead of editing) > that: > * MercurialEclipse will no longer "see" a default repo for your project, > * if you set the default repo via MercurialEclipse, be sure to know your > password because it can not be retrieved via the plugin. > > To sum up, it is safe to edit or delete default repositories, provided > that one has their passwords noted somewhere else. > > Regards, > -Amenel. > > 2017-05-16 0:57 GMT+02:00 Jay Ballinger <[email protected]>: > >> Howdy, >> >> >> >> I recently redefined an eclipse project to use a different repo. I was >> pointed to a private repo, but then deleted the .hg dir, performed hg init, >> and added in a .hg/hgrc file pointing to the team repo. >> >> >> >> This all works except for MercurialEclipse still defaults pushes to my >> private repo. The pop-up in the dialog allows me to choose the team repo, >> but I would rather it forgot about the private repo. >> >> >> >> Grep'ing through the eclipse workspace files, I find reference to the old >> repo in the ./.metadata/.plugins/org.eclipse.core.runtime/.settings/com. >> vectrace.MercurialEclipse.prefs. I see it listed a couple of times. What >> harm will I cause if I twiddle this file? How can I clean it up? >> >> >> >> *Jay Ballinger* >> >> UC Systems Architect >> >> University of California | UC Risk & Safety Solutions >> >> [email protected] | 530.554.1373 <(530)%20554-1373> | >> risksafety.universityofcalifornia.edu >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "MercurialEclipse" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "MercurialEclipse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
