Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 339724

Summary: [releng] Add source reference headers to the orion bundles
Product: [ECD] Orion Reporter: Andrew Niefer <aniefer>
Component: ClientAssignee: Project Inbox <e4.orion-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: tomasz.zarna
Version: 0.2   
Target Milestone: 0.2   
Hardware: PC   
OS: Linux   
Whiteboard:
Bug Depends on: 296082    
Bug Blocks:    

Description Andrew Niefer CLA 2011-03-11 12:10:37 EST
Susan said this:
> Maybe folks like John who don't need daily disruption should be pulling a specific tagged version of the client????


We should add the Eclipse-SourceReference header to our manifests.
Then, people would want to play with source but not necessarily track the most recent stuff, could do an Import -> Plugins & Fragments and get the specific version of the source corresponding to the bundles in their target.

This is all assuming appropriate egit support.  I took a brief look at the egit bundle used in our build and it does appear to at least attempt support for the Source Reference header.
Comment 1 Tomasz Zarna CLA 2011-03-14 04:54:25 EDT
In case of EGit importing their plug-ins could be a problem. To get the source from a repository pointed by Eclipse-SourceReference PDE uses Team API for importing .psf files. Currently, EGit does not support that, see bug 296082.
Comment 2 Andrew Niefer CLA 2011-03-17 17:34:31 EDT
This is done, bundles will now have the Eclipse-SourceReference headers as generated by org.eclipse.egit.fetchfactory.

As Thomas says, you can't actually import the bundles from Git because this is not yet supported by egit.  I have marked this bug as depending on bug 296082 since the original intent was to simplify people getting the correct source code.