431261 – Provide a way to discover where a plug-in resides (in which repository)

Bug 431261 - Provide a way to discover where a plug-in resides (in which repository)

Summary: Provide a way to discover where a plug-in resides (in which repository)

Status:	ASSIGNED

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Doc (show other bugs)
Version:	4.4
Hardware:	All All

Importance:	P3 enhancement (vote)
Target Milestone:	---
Assignee:	Platform-Doc-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-03-26 12:08 EDT by Terry Parker
Modified:	2014-04-01 09:22 EDT (History)
CC List:	1 user (show)

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 Terry Parker

2014-03-26 12:08:27 EDT

When creating a repository that aggregates all of its installation dependencies, tracking down repositories for missing dependencies can be a huge time sink. Having a global map of bundle/versions to repositories would be a valuable service, for both developers of repositories and for end users who encounter missing/broken repository associations (e.g., an associated repository has moved).

Universal use of Eclipse-SourceReferences in bundle manifests does not solve this problem, because the issue is that you don't have the bundle and don't know where to find it. Eclipse-SourceReferences can however be used to help generate the mappings.

There are several ways to provide and maintain these mappings, but the important point is to create a central resource that can be used to quickly discover the required repositories. If properly publicized, even a crowdsourced solution could be very effective.