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

Bug 350232

Summary:	source code management clients in EPP packages
Product:	[Technology] EPP	Reporter:	Markus Knauer <mknauer>
Component:	Packager	Assignee:	Project Inbox <epp.packager-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	jonah, mknauer, steffen.pingel, wayne.beaton
Version:	1.4.0
Target Milestone:	later
Hardware:	PC
OS:	All
Whiteboard:
Bug Depends on:	348875, 350079, 350621
Bug Blocks:

Description Markus Knauer

2011-06-24 07:06:26 EDT

Discuss and decide which SCM systems should be in which package.

Available clients:

* CVS - the good old implementation that is currently included in all packages
* Git - included in some but not all packages
* SVN, Subversive - in none of the packages but with the request to be included in one

To me it is not clear if we need all of them in all packages, but maybe it makes sense if the overall size is not too much. In that case I would suggest to remove the CVS configuration from all packages and create another grouping feature with the above SCM clients and add this to all packages. But as I said: I am not convinced that everybody needs all of them, maybe it makes sense to add EGit to the JavaScript package but not to the Java EE package. My guess is that most Java EE developers are using this package within companies and most of them are using Subversion internally (and not Git).

Would it be possible to use the Usage Data Collector to get some insights how many people are installing/using which SCM systems on certain packages, i.e. is EGit being used by developers using the RCP/RAP package, how many developers are installing Subversion tooling on top of the Java EE package, etc.

Comment 1 Steffen Pingel

2011-09-26 12:47:32 EDT

My sense is that Git will become the most relevant SCM integration. At this point it probably still makes sense to include CVS but in the future I could see that being an optional component that is installable through the Marketplace such as SVN support.

Comment 2 Wayne Beaton

2012-04-27 10:41:51 EDT

Just putting this out there...

We are in a constant struggle to balance download size, install footprint, and breadth of functionality.

Based on a very small sample size, my sense is that there is a huge portion of our community that does not know that you can easily extend Eclipse. Subversive and EGit are readily available and can be easily installed from the Eclipse Marketplace.

Is there some way that we can draw more attention to the marketplace client?

e.g. 

Open it on the "Popular" tab the first time Eclipse runs?

Make it more obvious on the overview page?

Add it to the Welcome page?

Add a hint/tip about it on the downloads page?

One wrinkle is that the CVS provider is not currently in the Marketplace AFAICT.

Just musing, but... maybe we can consider extending MPC to have a "recommended" tag that presents a hard-coded list of recommended additions from the package maintainer. i.e. "For this package, we recommend the following extensions..."

Of course, having a proper installer would be another way that we can present package maintainer recommended extensions...

Comment 3 Jonah Graham

2021-05-07 10:21:42 EDT

The EPP project does not have its "own" Packager anymore. EPP uses other technologies, such as Eclipse Tycho, Maven and Eclipse PDE. Therefore any remaining bugs are now being closed as WONTFIX. If this bug is still relevant, please make a comment and we'll move it to the correct project/component for further investigation.

This change was made as part of a bulk change.