Assembla home | Assembla project page
 

Ticket #6 (closed defect: fixed)

Opened 5 months ago

Last modified 3 months ago

https authentication glitches

Reported by: lorenzo@sancho.ccd.uniroma2.it Assigned to: bastiand
Priority: normal Milestone: 1.0
Component: mercurialeclipse Version: 1.0
Severity: normal Keywords:
Cc:

Description

There are some glitches in managing projects on shared http[s] repositories:

1. in clone dialog, it isn't possible to set the username/password to clone as in pull dialog 2. in pull dialog, if I press "next" instead of "finish", the username and password I've set are ignored 3. ditto for syncronize: the dialog is missing the fields for setting username and password

The plugin is great... I just hope there is a way to have these glitches fized before 1.0

Attachments

eclipseHgClone.png (72.8 kB) - added by anonymous on 07/18/08 18:28:25.
eclipseHgPull.png (63.7 kB) - added by anonymous on 07/18/08 18:29:06.
eclipseHgPullNext.2.png (92.9 kB) - added by anonymous on 07/19/08 10:37:04.
eclipseHgPullNext.png (92.9 kB) - added by anonymous on 07/19/08 10:39:08.

Change History

07/18/08 18:28:25 changed by anonymous

  • attachment eclipseHgClone.png added.

07/18/08 18:29:06 changed by anonymous

  • attachment eclipseHgPull.png added.

07/19/08 09:36:54 changed by anonymous

I forgot another small suggestion: if possible, I would like being able to set URLs like

https://user@hg.host.net/branch

and being prompted for the missing password.

07/19/08 10:37:04 changed by anonymous

  • attachment eclipseHgPullNext.2.png added.

07/19/08 10:39:08 changed by anonymous

  • attachment eclipseHgPullNext.png added.

07/19/08 10:56:41 changed by bastiand

  • owner changed from somebody to bastiand.
  • status changed from new to assigned.

Thanks for your report. I'll try to fix these issues before the release (meaning within the next two days :-)).

07/19/08 13:13:31 changed by bastiand

  • component changed from component1 to mercurialeclipse.

07/19/08 15:43:46 changed by bastiand

  • status changed from assigned to closed.
  • resolution set to fixed.

fixed in r736

07/19/08 15:46:23 changed by bastiand

uh...meant r735.

07/20/08 09:37:45 changed by bastiand

  • version set to 1.0.
  • milestone set to 1.0.

07/20/08 14:28:27 changed by bastiand

notification test

09/16/08 00:51:26 changed by anonymous

about their apps in the first place. Both annotations and contributions will only clutter the interface by default as a design pattern rather than trying to put it all together. That way you can never create offline or print docs of high quality without again having the devs or current admins maintain the comments and annotations. Hopefully a small Wiki quality team will evolve (i am against ops or admins) to review and summarize the contributions. I hope this gives us more users as contributors than having the docs focused on the devs. Cheers, duns china tour Apparel shoes bags Kitchen Food and Wine Furniture) Flowers and Gifts Wall Art Computer Components I still prefer a wiki like approach since the php (or mysql) docs are very cluttered when you have to take their comments in account. On the other hand they are professionally maintained imho, since they are *much* better than KDE documentation. KDE is by far larger and has so many different apps, which need screenshots and end user not dev/api docs, that more help is needed as long as the devs prefer to code than to write nice docs. And it is their choice to some degree imo. Technically interested but non-dev end users, which are plenty out there, are the users of and the best contributers to the docs

Add/Change #6 (https authentication glitches)




Action