How JMPS settings for upstream TSs should be detected? Some options that came from the discussion on the analysis. Some TS needs to add some specific add-opens/add-export parameters, but this issue is not about it. This issue is about defining the basic set of add-opens & add-export parameters, those needs to be added always.

• hardcoded in pom.xml of TSs without any synchronization
  • used for both client and server side
• Properties from WF-Core launcher will be used
  • for server side only, what about client side in this case?
  • WF-core version is hardcoded in arquillian-container. But wf-core version can be override in pom files. Should that version be override in that case? If not, JPMS properties may be outdated anyway.
• Get properties from scripts
  • extra configuration & maintenance needed
  • JPMS settings from the launcher needs to be disabled (not possible now, but will be possible if this code will be parametrized)
  • PoC

    source ~/wildfly-2022-03-30/bin/common.sh
    JAVA=java
    setDefaultModularJvmOptions
    mvn test ... "-Dserver.jvm.default.add.package.args=${DEFAULT_MODULAR_JVM_OPTIONS}"
    

• something else

—

Related question:

• Is there a requirement that JPMS properties from WF launcher needs to be synced with properties from common.[sh|bat|ps1].
• Requirements for JPMS settings for client side needs to be described in the analysis, see some details here