Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Remove CVS from Eclipse packages?

I would suggest keeping it in “Standard” as long as the Eclipse Orbit project still uses CVS.

“Standard” should continue being the one-stop-shop for self-hosted development of Eclipse Plugins.

The CVS adapter is really small enough to not cause any harm IMHO.


Moving it out of the other packages, and offering CVS on the Marketplace instead, is a good idea.

Marketplace Statistics will also give some idea how many people still want it.





Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River

direct +43.662.457915.85  fax +43.662.457915.6


From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Moritz Eysholdt
Sent: Thursday, June 26, 2014 11:16 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Remove CVS from Eclipse packages?




yes! let’s get rid of this dinosaur!





On 26 Jun 2014, at 10:24, Mickael Istria <mistria@xxxxxxxxxx> wrote:

Hi all,

Now that CVS is only used by 3.7% of people according to latest Eclipse survey, wouldn't it make sense to kick it out of default Eclipse packages to avoid showing the useless CVS entries (in show view or import for example) to the remaining 96.3% of Eclipse users? Instead, we could think of providing CVS on marketplace.

What do you think about it?

Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

cross-project-issues-dev mailing list


Back to the top