[Solved]-Best strategy / practice for publishing an Eclipse plugin that requires larger-than-default JVM heap?-eclipse

there seems to be now way to augment heap space at runtime (confirmed by this so question)

so, a run time check at active state of this osgi bundle should be the only option (with a visible warning, a log entry in the error view and an instant stop from this plugin)

check -xmx setting when your plugin is first run, and propose to automatically increase it if it's too low. (just write the changes directly to eclipse.ini.)

there is no other way as far as i know.