Re: [cross-project-issues-dev] New "repository reports": Eclipse-SourceR

[Thomas Hallgren <thomas@xxxxxxx>]

I'm a bit concerned that neither Subversive nor Subclipse seems to support this at the consumer end. Buckminster is capable of generating the Eclipse-SourceReferences header for CVS, SVN, and Git, but the ones we generate for our own bundles (currently SVN) does not show up in the import wizard. Not sure what the story is with Git but I know it wasn't implemented a couple of months ago.

I think it would be unfair to add this until it's fully supported by at least Suversive and Git. Once that's in place, it's a different story.

Regards,
Thomas Hallgren


On 2011-06-03 13:14, Paul Webster wrote:

On Thu, Jun 2, 2011 at 11:31 PM, David Carver <d_a_carver@xxxxxxxxx> wrote:

Personally, I wouldn't make it a Should Do.  There are other ways to get the sources.

There are other, difficult, ways to get the sources.
 

I'd rather try to get away from anything that is tied to a particular version control, or a particular set of build technologies,

This isn't tied to a particular version control system or a particular set of build technologies, but a particular set of tooling in the IDE ... PDE to be exact.  IIRC the format was picked to be maven compatible [1].

Since most of the projects in question use PDE, and most people developing eclipse plugins use PDE, I think it's fair to make this a +1 (I'm fine with opting out if their not providing an eclipse plugin).  If I want to patch a project properly, I need to check the source out of the SCM (CVS, SVN, Git, etc) and this provides a mechanism to go straight from your Target Platform to the correct source used to build it.

[1] Bug 243582 - Support embedding repository information in released bundles

--
Paul Webster
Hi floor.  Make me a sammich! - GIR

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev