Bugzilla – Full Text Bug Listing
| Summary: | Support parsing and materializing Eclipse-SourceReferences within EGit | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Alex Blewitt <alex.blewitt> |
| Component: | UI | Assignee: | Project Inbox <egit.ui-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | mknauer, mober.at+eclipse, stefan.lay |
| Version: | unspecified | ||
| Target Milestone: | 2.0 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 450835 | ||
|
Description
Alex Blewitt
I think this is possible with egit-2.3.1 using the "EGit Plug-In Import Support" optional feature so the bug might be closed fixed ? When I launch Eclipse Classic SDK, open the Plug-Ins View and Import As... Project from a Repository, I can "Import from Master" any plug-in. The "Import Specific Version" does not seem to work, neither with this SCMURL using a tag: Eclipse-SourceReferences: scm:git:git://git.eclipse.org/gitroot/platfo rm/eclipse.platform.resources.git;path="bundles/org.eclipse.core.file system";tag=v20130122-153237 Nor with that one (generated by Tycho), using a commitId: Eclipse-SourceReferences: scm:git:git://git.eclipse.org/gitroot/tm/org .eclipse.tm.git;path="terminal/plugins/org.eclipse.tm.terminal.ssh";c ommitId=447db14467e609c796db6deec395cd6bacf376d8 Parsing and Materializing Eclipse-SourceReferences is actually supported since EGit 2.0 : http://wiki.eclipse.org/EGit/New_and_Noteworthy/2.0#Support_for_Eclipse-SourceReferences_manifest_headers Generating them through CBI/Tycho is supported since Tycho 0.16.0: https://bugs.eclipse.org/bugs/show_bug.cgi?id=380872 http://wiki.eclipse.org/Tycho/FAQ#How_to_generate_Eclipse-SourceReferences_MANIFEST_header.3F Missing support for "Import a specific version" is tracked in bug 367712. So, I think this can safely be closed. |