Bug 1505 - Seamless support of OpenJDK 2x; Mitigating its Constraints and support its Features

Certain forum posts reported various issues using OpenJDK 2x
running JogAmp in conjunction with user applications.

This in regards to old and new JVM launch parameter like 'add-opens'
and the module system, we so far have simply ignored.

However, new launch parameter in OpenJDK 2x might also appear
which further reduce convenience of mix-and-match libraries, native code and modules.

Please add information in this regard under this bug report,
so we may be able to address these inconveniences and to keep using
OpenJDK for your mixed application feasible.

+++

My initial idea of creating a convenient custom launch pack
is to use a JVM Launch Pad (JLP, native code or preferably Java itself),
which simply adds required parameters to the launched JVM depending
on OS and JVM version.

Additionally, this JLP could be packed within our JogAmp fat jar file
and use an environment variable and/or property setting specifying
the actual target main class for the newly launched JVM.

This would allow to re-use our JogAmp far jar file to repackage
your application by injecting all your libraries and application classes
in one jar file and setting mentioned target main class property.

The end user then could just launch the application as usual via
'java -jar lala.jar'