JPMS properties are currently hardcoded in a launcher. Launcher is used by arquillian container. But latest version of arquillian container uses wf-core 16.0.0.Final. So if we depend on old wf-core launcher, we can't ensure that proper JPMS settings would be used. Fortunately, it's quite easy to propagate correct JPMS properties to arquillian directly. This would be useful only if hard-coded properties from Launcher won't be used. This task adds option to not use hard-coded properties from launcher.

The default settings will be still the same - hardcoded JPMS properties would be used by default.

cc: jperkins-rhn, bstansbe@redhat.com