[ https://issues.jboss.org/browse/WFLY-11226?page=com.atlassian.jira.plugin... ] Michal Jurc updated WFLY-11226: ------------------------------- Description: 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. was: 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 message was sent by Atlassian Jira (v7.12.1#712002)