[
https://issues.jboss.org/browse/WFLY-10512?page=com.atlassian.jira.plugin...
]
Jean-Francois Denise commented on WFLY-10512:
---------------------------------------------
I can reproduce by using jre10 instead of jdk10 both with ps1 and bat file on Windows. As
you wrote, with wildly12, jboss-cli can start with jre. Something changed in jboss
modules. Investigating.
For now be sure to set JAVA_HOME to jdk10.
jboss-cli.ps1 not working (possible regression)
-----------------------------------------------
Key: WFLY-10512
URL:
https://issues.jboss.org/browse/WFLY-10512
Project: WildFly
Issue Type: Bug
Components: CLI
Affects Versions: 13.0.0.Final
Environment: Java 10.0.1 (oracle server-jdk), Windows 10
Reporter: Martin Miller
Assignee: Jean-Francois Denise
Under an environment with a JAVA_HOME to java 10.0.1,
I can start the jboss-cli.ps1 under Wildfly 12, but under Wildfly 13 I get:
org.jboss.modules.ModuleNotFoundException: jdk.jconsole
at org.jboss.modules.Module.addPaths(Module.java:1266)
at org.jboss.modules.Module.link(Module.java:1622)
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
at org.jboss.modules.Main.main(Main.java:437)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)