Bugzilla – Full Text Bug Listing
| Summary: | [CVS Core UI] EXT: provide ui for configuring ext parameters on location | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jean-Michel Lemieux <jean-michel_lemieux> |
| Component: | Team | Assignee: | Platform-VCM-Inbox <platform-vcm-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | alex.blewitt |
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | other | ||
| Whiteboard: | |||
|
Description
Jean-Michel Lemieux
The UI for configuring the EXT method is in the preferences. It would be cool if when you selected 'ext' in the repo connection wizard that you could right there and then confirm/change the ext settings. It is bogus that when you are in one wizard and press finish you have to intuitively know that to finish the workflow you must go somewhere else to configure something. Now supported as global preference. Reopen if: - there are other parameters we need - you feel strongly that it should be supported at per location level, as PR states - we have partial sufficient solution now. - per location basis is post 2.0 (post 2.0) Reopening I think true per-location ext setup is as bogus. The parameters that we now set globally, are where to find the ssh client executable (be it plink, openssh/cygwin, whatever) and how to call it (parameter syntax). Per-location setup of these is needed if the user wants to use different ssh clients for different locations; and I don't feel this is the main problem, nor what Jean- Michel originally complained about. The real problem is that when the user is using the connection setup wizard, there is nothing that tells him what the ssh client settings are or how to change them; nothing even telling him such settings exist. Moving these preferences from global to per-location won't be good either, because for every location, the user will need to remember again what the correct settings were. I think the right way is to _provide information_ about the global setting on the location setup page, with a button opening the preferences page if the user wants to change it. So far I was ignoring the "cvs command" setting. This is different. What I don't understand is why this is particular to ext. It should be per-location, and is connection-method-independent. For an example of a reason to want per-connection configuration: bug 6892 Improvements needed to this UI anyway: bug 35304 I think the reason "cvs command" is specific to :ext: is that :ext: is the connection method that works by opening a command-shell connection somewhere and running a cvs command in that shell. Other connection methods don't necessarily; for example a pserver connection just expects to connect to a port and find a pserver listening there. I agree with B. Shingarov that the "cvs command", at least for :ext:, should be configurable per location. It is a property of how cvs is named and found on the machine you are connecting to, which can vary from one to another. *** Bug 36322 has been marked as a duplicate of this bug. *** This should be addressed before the next release. Post 3.0 This is less of an issue now that extssh supports SSH2 One thing that's really annoying with the :extssh: method is that no other CVS client knows how to handle it. As a result, if you drop down into the command shell and do (e.g.) cvs update, it complains that :extssh: is unknown. You can configure the ext conection method to use extssh inside Eclipse. This allows you to use both Eclipse CVS and another CVS. You can configure this on the TEam/CVS/EXT Conection Method preference page. |