Unify interface between java.so and CLI java

[tgrabiec]

Currently there is no way to set system properties on app level when starting directly with java.so. The -D arguments will be passed to the JVM, not to the isolate launcher. Hence they will be globally accessible.

Example:

image command line:

java.so -Dname=node1 my.App

CLI command line:

java -Dname=node1 my.App

In the first case all apps inside the JVM will see the "name" property, whereas in the second case only the started app will.

I think java.so should behave the same as CLI case. Just because we start some app from the beginning doesn't mean all apps must share that app's config.

However there still may be a need to set system properties on JVM level. I propose to adopt a scheme which is present in other tools out there. Options prefixed with -J will be always passed to the JVM, eg:

java.so -J-Dglobal=value my.App

[wkozaczuk]

Given that we are very close to run completely unmodified JRE which does not need Java wrapper I suggest we close this issue.

[nyh]

I suggest we leave those "isolate" issues until we decide to completely remove this "isolate" feature.