Description John Arthorne 2008-01-08 22:48:21 EST

The terminology "implementation only" for repositories that are hidden implementation details of the framework is awkward. We also had a need recently to talk about the inverse of this concept, "non-implementation-only" repositories in the IMetadataReposiotryManager API (which we tentatively called "public repositories"). 

I'd like to change the terminology to "system repository", much like we have "system jobs" for hidden jobs, the "system bundle" in OSGi to represent the framework bundle, or the system menu in dialogs. We can then avoid introducing the new term "public repository" and use "non-system repository" where necessary to refer to repositories that are not system repositories.