Status: Closed (View Workflow)
Set these memory limits in your eclipse.ini file, and restart Eclipse 3.6.2:
Not sure if this qualifies as a bug or a feature request but
I noticed that if I use JBDS 4 updatesite against plain Eclipse things seem to work great
until you restart (possible on the second restart) since then it suddenly has zero
extra memory allocated.
It only started working properly when using the jbdevstudio.app; thus my assumption is that
eclipse.ini is ignored and jbdevstudio.ini is looked for instead but this file is nowhere
to be found (except inside jbdevstudio.app)
Would be good if we could handle this situation more gracefully since the shortcuts users
uses still points to eclipse thus they will see it as JBDS running out of memory since when launching
it says JBDS.