Summary: | Unable to specific custom CVS authenticator | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Troy Bishop <tjbishop> |
Component: | CVS | Assignee: | platform-cvs-inbox <platform-cvs-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | melickm, Michael.Valenta, tomasz.zarna |
Version: | 3.2.2 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Troy Bishop
2008-07-10 17:03:00 EDT
Regarding question 2) please take a look at bug 204548 where Michael explains briefly how and why the authenticator extension point works. Ignore comment 1 as it refers to a different authenticator. If you are trying to import headless, the best way to accomplish what you want is to remove the CVS/UI plug-in from your install. You can then register your own authenticator which should get picked up since the UI authenticator would no longer be available. Michael has provided a work-around where we are able to setup the CVS repository before doing the project set import. This is a reasonable work-around however the better long-term solution would be to allow us to implement our own headless CVS authenticator. Given that this would be a feature enhancement I am changing the severity to 'enhancement'. Thanks Michael for the work-around that we can use for now: boolean isKnown = KnownRepositories.getInstance().isKnownRepository(repositoryLocationWithUserId); CVSRepositoryLocation location = null; try { location = (CVSRepositoryLocation) KnownRepositories.getInstance().getRepository(repositoryLocationWithUserId); } catch (CVSException cvsEx) { ... } if (!isKnown) { location = (CVSRepositoryLocation) KnownRepositories.getInstance().addRepository(location, false); } location.setPassword("password"); location.updateCache(); 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. |