Community
Participate
Working Groups
Created attachment 107351 [details] Changes some data members from private to protected access If some data members of the CVS Checkout Wizard were made protected, it would then be possible to create custom wizards for specific repository locations, effectively removing a lot of the clutter when selecting a specific repository location. I have attached a simple patch for this.
Elliot what are you missing in the current Checkout Wizard? Maybe this is something we could use for all locations.
Merely the need to create a custom wizard that parses an SSL certificate which it uses to get the username for the repository location and then having only this location appear to select. The wizard is to be part of a plugin for Fedora hosted projects where there is an option to checkout from Fedora CVS, mimicking the ease of use of the command line utility provided for our package maintainers.
Sounds like a cool feature. Are you going to use the certificate only to get the username? Correct me if I'm wrong but is this the same kind of certificate as the ones from "SSH2 > Known Hosts" preference page? Can all these certificates be parsed the same way (ie Do they have a standardized content? I guess they do)? What do you think about adding it to the current "Import from CVS wizard"? Is there anything I can help you with (except modifying our internal classes)?
Changing Version tag to something more believable. Note that this is not a statement about when the enhancement request will be addressed (the Target Milestone field is used for that); the Version tag should be set to the version of Eclipse you were using when you saw the need for the enhancement.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
