[
https://issues.jboss.org/browse/WFLY-11226?page=com.atlassian.jira.plugin...
]
James Perkins commented on WFLY-11226:
--------------------------------------
Note that there is no effect on deployment goals. The {{run}}, {{start}} and
{{execute-commands}} goals should be the only ones that have this issue. As a workaround
you can add the following to a pom.
{code}
<profile>
<id>java9-plus</id>
<activation>
<jdk>[9,)</jdk>
</activation>
<plugins>
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-maven-plugin</artifactId>
<version>1.3.0.Alpha1-SNAPSHOT</version>
<configuration>
<java-opts>
<java-opt>--add-modules=java.se</java-opt>
</java-opts>
</configuration>
</plugin>
</plugins>
</profile>
{code}
Maven Wildfly plugin should be working with Java 9+
---------------------------------------------------
Key: WFLY-11226
URL:
https://issues.jboss.org/browse/WFLY-11226
Project: WildFly
Issue Type: Bug
Affects Versions: 14.0.1.Final
Reporter: Michal Jurc
Assignee: James Perkins
Priority: Blocker
Labels: java11
Without the workaround, the following error is thrown by JVM upon starting WildFly/JBoss
CLI utilising the plugin:
{code}21:35:19 [INFO] STANDALONE server is starting up.
21:35:20 org.jboss.modules.ModuleNotFoundException: java.se
21:35:20 at org.jboss.modules.Module.addPaths(Module.java:1266)
21:35:20 at org.jboss.modules.Module.link(Module.java:1622)
21:35:20 at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
21:35:20 at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
21:35:20 at org.jboss.modules.Main.main(Main.java:437){code}
This is pretty cumbersome and a blocker to migrating application without change of
configuration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)