Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PDE/Importing SCMURLs"
(New page: == Overview == SCM URLs describe the location of source code in a repository. For example, an SCM URL can be used to describe the location of a project in CVS that corresponds to a bundl...) |
(→3.6 Implementation) |
||
| Line 12: | Line 12: | ||
== 3.6 Implementation == | == 3.6 Implementation == | ||
| + | The 3.6 implementation for importing bundles from repositories is based on the following (internal) extension points: | ||
| + | |||
| + | * '''org.eclipse.pde.core.bundleImporters''' - Extensions contribute delegates that when given a set of bundle manifest headers can return a corresponding set of opaque ''bundle import description'' objects that can later be imported. Extensions provide an implementation of IBundleImportDelegate (defined in org.eclipse.pde.internal.core.importing.provisional). | ||
| + | * '''org.eclipse.pde.ui.bundleImportPages''' - Extensions contribute one or more wizard pages used to configure ''bundle import description'' objects before import. For example, the existing implementation provides a page that allows the user to import specific project versions or from HEAD. | ||
== 3.7 API Proposal == | == 3.7 API Proposal == | ||
Revision as of 15:51, 20 September 2010
Overview
SCM URLs describe the location of source code in a repository. For example, an SCM URL can be used to describe the location of a project in CVS that corresponds to a bundle in Eclipse. The SCM URL format is described here.
In Eclipse 3.6, support was added to PDE/Build to embed source repository information in bundle manifests during the build process and support was added to PDE/UI to import bundles from repositories. Following is an example manifest header describing the location of the source for the org.eclipse.debug.core bundle:
-
Eclipse-SourceReferences: scm:cvs:pserver:dev.eclipse.org:/cvsroot/eclipse:org.eclipse.debug.core;tag=v20100820
The 3.6 implementation of importing bundles in PDE/UI is based on two internal extension points and internal API interfaces. During 3.7, PDE would like to create official public API that can be used.
3.6 Implementation
The 3.6 implementation for importing bundles from repositories is based on the following (internal) extension points:
- org.eclipse.pde.core.bundleImporters - Extensions contribute delegates that when given a set of bundle manifest headers can return a corresponding set of opaque bundle import description objects that can later be imported. Extensions provide an implementation of IBundleImportDelegate (defined in org.eclipse.pde.internal.core.importing.provisional).
- org.eclipse.pde.ui.bundleImportPages - Extensions contribute one or more wizard pages used to configure bundle import description objects before import. For example, the existing implementation provides a page that allows the user to import specific project versions or from HEAD.