-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 06.12.2008 um 14:53 schrieb codethief: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >>> > > Forwarded from codethief... > > ====== > > Hey guys, > > So yesterday, I experienced a hell of a lot of problems with > MercurialEclipse. > First of all, I created a repository inside of my project dir (i.e. > another repository) directly via hg. Obviously this failed: When I > refreshed the package explorer or did something to my repository > (commit, push, ...) I received error messages like that: > http://img338.imageshack.us/img338/3395/mercurialeclipseerrornh7.png > > Also, I was wondering why I couldn't just create a new repository in a > folder with MercurialEclipse? As far as I can see, cloning is the only > option at the moment? Eclipse doesn't have any infrastructure to support subrepositories that are situated in folders of projects. In Eclipse you can only assign team providers to projects - not to arbitrary folders. And currently, there's a lot of code that assumes the Mercurial repository is at project level or higher. I haven't tried it, but perhaps you get most functions working, if you add .hg/* to Eclipse's ignored resources. > > > Secondly, wasn't there an entry in the context menu ("Team") in former > times that allowed me to add files to .hgignore? There still is - but as your repository setup is not supported, it might be dynamically deactived and therefore not shown. We determine activation of menu items by using Mercurial's working directory status, so if that doesn't work, the menu will be broken. > > > Thirdly, when cloning a remote repository, my username and password > are still saved in the URI. Ok, passwords are hidden, yet I still > don't like the way the whole is managed. Because: When I'm using the > URI with username and password in it, I can't push to this repository > (bitbucket.org wiki repository) whereas when I'm using the plain URI > and fill out the username / password text fields, everything's fine. This would be a bug, that would need to be fixed. I'll see, if I can reproduce it. Giving authentication data on the URI should have the same effect as giving this information in the text fields. > > Furthermore I noticed that the usernames are still being stored > somewhere (Including an empty username popping up in the middle of the > username dropdown list and "hg" which are both wrong and which I both > don't need.) and still can't be deleted. This is not repository related, but most probably remembering of formerly entered values. Probably, we should provide an option to activate/deactivate this. > > > I could imagine the whole thing to work like this: > When committing, pushing, cloning, ... the user can just select > between the repositories already existing, but by clicking on a button > "Add repository" he can add another repository. There, he should have > several options, like repository URI, username, password and whether > only the username, both, username and password, or nothing should be > saved. That is, usernames / passwords aren't available for all > repositories but only for one. Besides, what about giving repos a > name? Storing passwords is hard. Even though Eclipse 3.4 supports a pseudo- encrypted password store, this is a) not really save and b) not compatible with Eclipse 3.3. That's why we currently don't persist passwords, but only store them in memory. Therefore, we need the authentication fields in the wizards. As for adding repositories, I wouldn't want this in the wizards - this would just clutter the interface even more. You can add repositories by using the repository browser view, and perhaps in the future in a project property page. Names for repositories would be a new feature that I like, but that we don't support so far. > > As for local repositories, you could also give an option like "Always > push to this repository:", because it's a pain in the ass to always > select the respective repo and if you're unlucky, you accidentally > select the wrong one (as the repo URIs are somewhat similar) and > push... :/ If you have a default repository defined in your hgrc file, this is preselected. This, at least, works for me :). > > Also, as indicated above, I'd love to have nested repositories, if > this possible at all and not limited by hg itself? Hg currently only supports repository nesting by using the forest extension. There's currently some development going on for bringing something like submodules to Mercurial, but it's still early in development. Moreover, even if Mercurial supported subrepositories, we'd have to think about how to do status decoration, merges, etc. Mercurial Eclipse supports the forest extension for push/pull/clone, but you would end up with one project per subrepositories due to above mentioned Eclipse conventions with team providers. > > > Additionally, somewhere in the preferences window the user should be > able to edit all these settings again for each repository. I think I've replied to this above :). > > > > Regards, > Simon Cheers, Bastian > > << > > > - -- > Simon Hirscher > Contact information: http://codethief.eu > - -- > Use my GPG public key for encrypted emails: http://codethief.eu/public_key.asc > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.8 (Darwin) > > iEYEARECAAYFAkk63wYACgkQBqJW4lDO0YKC0QCeJAwnywVsbpum8eJ+vmFDiaPl > bNwAnjBrTE7wf6FSdpXW2Y08iAYhBg3n > =58Xu > -----END PGP SIGNATURE----- > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkk7vIcACgkQBqJW4lDO0YLUSwCgh0l2Orx652DTfXt35+Av7iy2 XDQAnRFSky6ySZyVyD4Lc3pbrRW8zEuo =MB14 -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MercurialEclipse" 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/mercurialeclipse?hl=en -~----------~----~----~----~------~----~------~--~---
