[jbossts-issues] [JBoss JIRA] (JBTM-3122) jbosstm/quickstarts tests can't be run with jdk9+

[Ondra Chaloupka (Jira)]

     [ https://issues.jboss.org/browse/JBTM-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondra Chaloupka updated JBTM-3122:
----------------------------------
    Summary: jbosstm/quickstarts tests can't be run with jdk9+  (was: jbosstm/quickstars can't be run with jdk9+)


> jbosstm/quickstarts tests can't be run with jdk9+
> -------------------------------------------------
>
>                 Key: JBTM-3122
>                 URL: https://issues.jboss.org/browse/JBTM-3122
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Build System
>    Affects Versions: 5.9.3.Final
>            Reporter: Ondra Chaloupka
>            Assignee: Ondra Chaloupka
>            Priority: Major
>
> Quickstarts do not run tests with JDK9+. We use the Arquillian that starts the WildFly and for the JDK9+ it requires JVM options to add module permissions (and more).
> The quickstarts need to start using a profile, similar how WFLY uses it, that defines jvm args that will be passed to the `arquillian.xml`.
> See https://github.com/wildfly/wildfly/blob/16.0.0.Final/pom.xml#L7188
> {code}
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED
> --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED
> --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED
> --add-modules=java.se
> {code}
> The trouble in quickstarts is that we have no parent for the quickstarts so we need to add such profile to all the `pom.xml` files all over the quickstarts.
> Maybe we should provide a parent with such settings. We can unify not only this but e.g. ee version used or arquillian version.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)