If PDT is correctly depending on EMF *plugins* instead of *features*
then only the minimum required plugins and their much-smaller-containing
features will be used. This change was done for WTP's benefit last year
-- PDT ought to do the same, as it depends on WTP in turn.
I recommend opening a bug against PDT asking that they depend on the
smaller EMF features and/or just the plugins. Then your install
experience will be much smaller.
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=PDT
Post this link in the bug for their reference:
http://wiki.eclipse.org/EMF/EMF_2.3/New_Features_Migration_Guide
Cheers,
Nick
Jacob Fogg wrote:
Any way to package that? I am sure there are a LOT of people who
would be interested!
Hertzel Armengol wrote:
HI I'm just trying to create my perfect PDT env, an for achieving
that I need to trim the base core eclipse system, but in order to do
it I need to know exaclty which packages does PDE require to work
EMF for example is a big framework and im pretty sure that yuy're not
using it at it's fullness .
so far I have removed
java, ant, cvs, a few emf, and others... and my eclipse just eats
6mbs of ram without any open project now, nice huh :)