> Standard use to be the SDK plus git and MPC. It was for people who just want the basics and to build up their environment to suit their needs.
If that’s the goal, the current composition of the Standard package is a very poor solution as it contains PDE and source, neither of which are of any use to most Java developers downloading Eclipse. Consider that the Standard Package is 200MB to Java package’s 153MB and Standard doesn’t even have Mylyn or m2e.
Since there clearly aren’t 3 million plugin developers out there, most of these downloads represents users downloading the Standard package out of confusion or due to its default/prominent placement and getting more than they need. Why do we need a bug to acknowledge that there is a problem? The stats speak for themselves.
- Konstantin
From: epp-dev-bounces@xxxxxxxxxxx [mailto:epp-dev-bounces@xxxxxxxxxxx] On Behalf Of Ian Skerrett
Sent: Monday, May 05, 2014 9:57 AM
To: 'Eclipse Packaging Project'
Subject: Re: [epp-dev] Java package
I think it might be useful for people to look at the history of the Standard package. Read the gory details at https://bugs.eclipse.org/bugs/show_bug.cgi?id=397896
Tl;dr; Standard use to be the SDK plus git and MPC. It was for people who just want the basics and to build up their environment to suit their needs. I really don’t think should change from this strategy. Based on the download numbers, people also seem to like it. For some reason people on this thread seems to think there is confusion in the Eclipse community. Can someone point to a bug where this confusion is recorded?
Right. Another example of confusing labeling. Arguably, that one should be just “Eclipse IDE for RAP Developers”. I would doubt that standard RCP developers are interested in that package. That’s not the only example where this naming pattern is causing unnecessary confusion. We have two packages labeled “Java and X”.
- Konstantin
I think “Plugin Developer might be more clear in that respect.
There is also a package for RCP and RAP developers….