Bug 21545 - Global Preferences Page needs to support Repository AccessSpecs
Summary: Global Preferences Page needs to support Repository AccessSpecs
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Stellation (show other bugs)
Version: unspecified   Edit
Hardware: Other other
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Jim Wright CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-12 12:51 EDT by Jim Wright CLA
Modified: 2005-08-31 16:38 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Wright CLA 2002-07-12 12:51:56 EDT 
Stellation Plugins use the ScmAccessSpec class to encapsulate all the 
information needed to access a repository.  Currently, these can be created and 
configured only while using the ScmConfigWizard (e.g. while configuring an 
Eclipse project to use Stellation).  It should be possible to create and modify 
these AccessSpecs from the global Stellation preferences page.

Note: the set of configured AccessSpecs is maintained on a per-installation 
basis.  Once created, an AccessSpec is available in future Eclipse sessions on 
the same machine (using the same Eclipse workspace or a different one).
Of course, deleting the Eclipse plugin metadata area will also delete the set 
of AccessSpecs.