As an alternative we could replace „Standard“ with an „Ultimate Java“ Edition (including J2EE, WTP, RCP, Modeling) and see what the download numbers are next year.
See I totally agree that are places where you want to specialize. My only problem that we are discussing this among ~ 1000 eclipse committers here and we have around 2 mio downloads.
Maybe its also because I do a lot of RCP development and always download the RCP packages for the Eclipse IDE. Recently I decided to do some WTP stuff for myself. And the easiest way for me was to download a WTP Eclipse IDE. So maybe you can say that I could have downloaded some features from the Kepler repo. But I wasnt sure what was necessary so I downloaded a new IDE. (Felt strange, but worked)
So after that I thought, maybe I would preferred an IDE that can do „everything java“ aka „ultimate“...
christian
Von: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] Im Auftrag von Mickael Istria
Gesendet: Dienstag, 30. Juli 2013 16:12
An: cross-project-issues-dev@xxxxxxxxxxx
Betreff: Re: [cross-project-issues-dev] Are too many packages actually hurting Eclipse?
On 07/30/2013 03:57 PM, Igor Fedorenko wrote:
Are you suggesting forcing webtools on all java developers? Seriously?
I've just had a new look at the Eclipse community survey and since about 45% (~=100% - web dev perventage - RCP percentage - non-Java users percentage) of Java users are doing something else that Web or Plugin development, it seems indeed that a Java package without WTP makes sense.
The use cases are people doing some server side stuff and plugins for various non-web applications (Maven, Jenkins, Ant...).
So I'm changing my mind and now agree that two distinct "Java" and "Java for Web development" package would still make sense. However I still keep thinking that "Eclipse Standard" doesn't help much.