Community
Participate
Working Groups
How about creating a really small MPC EPP package that contains only the bare minimum set of bundles that is necessary to run the MPC and to enhance this package?
Unless we made all of the Eclipse projects accessible through Marketplace, I am now sure how this would be useful?
Markus, can you please describe your use case?
Most EPP packages try to put everything that the package maintainer assumes to be useful into one package. While this is a good starting point for many users, it doesn't solve all problems, and there are problems with this approach: * The package size: It is easy to put features into a package, but you have a hard time stripping it down to the bare minimum. In most cases this leads to huge packages and whenever I read comments about new releases I see users complaining about the size of Eclipse downloads. * Too many features: This clutters the UI, slows down Eclipse, etc - I know there are strategies against this (activities, etc.) but who uses it? * eclipse.org content: The EPP packages contain only bits and pieces from the simultaneous release train, whereas the MPC allows to install additional features from external sources for the first time. These are just a few of the problems that I see today. Give me more time and I will come up with more ;-) The idea of such a 'MPC-only-package' would be to give new (experienced?) users the chance to start small and to build their own Eclipse working environment with the MPC by installing only what they need. That would give users the freedom to choose what they really need, instead of having a package maintainer doing this decision based on assumptions. And with the launch of the MPC it is the first time that users can do this easily. Of course, Ian is right that all Eclipse projects (or at least the project participating in the simultaneous release) should be installable with the MPC. But if we decide this we could try to make that a requirement for Indigo.
(In reply to comment #3) > The idea of such a 'MPC-only-package' would be to give new (experienced?) users > the chance to start small and to build their own Eclipse working environment > with the MPC by installing only what they need. That would give users the > freedom to choose what they really need, instead of having a package maintainer > doing this decision based on assumptions. And with the launch of the MPC it is > the first time that users can do this easily. Why wouldn't experience users just use the Helios repository? > > Of course, Ian is right that all Eclipse projects (or at least the project > participating in the simultaneous release) should be installable with the MPC. > But if we decide this we could try to make that a requirement for Indigo. I am still not clear how this is better than just using the release train repository?
Markus, I like the idea. I also wonder if such a "minimalist" package should replace the "Eclipse Classic" package on the downloads page? BTW, another option would be to just replace the "Eclipse Classic" package with a package containing the Eclipse SDK plus MPC (essentially the issue raised in bug 375292).
(In reply to comment #4) > I am still not clear how this is better than just using the release train > repository? The purpose could be to simply not have packages anymore (to reduce the important space wasted by duplicating bits over and over). I imagine one downloading a minimalist package and be presented with options to download & install the traditional packages via MPC instead. We also see users on the Newcomers forum who think that they need to download three different zip files in order to have a C++ IDE, a Java IDE and a PHP ide.
I think the new Eclipse Installer is going to accomplish the intent of this bug.
