Best strategy / practice for publishing an Eclipse plugin that requires a bunch of larger JVMs than the default?

Question

I am developing the Eclipse plugin and am going to start presenting it at conferences and other venues so that people can install it.

One limitation of the plugin is that, due to the amount of information that it must support in order to work, it requires more heap space than the default for Eclipse. Eclipse works with the minimum maximum heap even on computers with tons of RAM, and many developers have never bothered to fix this, especially when launching new versions.

If my plugin runs on a system with insufficient heap, it can slow down Eclipse.

What is the best strategy to solve this problem? Is there any official way through Eclipse? Checking runtime every time the plugin starts? etc.

Answer 1

There seems to be a way now to increase the heap space at runtime (confirmed by this SO question )

So, checking the ACTIVE state runtime of this OSGI package should be the only option (with a visible warning, a log entry in the Error view and an instant stop from this plugin)

Answer 2

-Xmx , . ( eclipse.ini.)

, .