cygwin jboss-cli.sh ------------------- Key: WFLY-2523 URL: https://issues.jboss.org/browse/WFLY-2523 Project: WildFly Issue Type: Patch Security Level: Public(Everyone can see) Components: CLI Affects Versions: 8.0.0.Beta1 Environment: windows 7 x64 / cygwin Reporter: Darko Palic Assignee: Alexey Loubyansky Labels: cli, cygwin Fix For: 8.0.0.Final Original Estimate: 1 hour Remaining Estimate: 1 hour On cygwin is the implementation of the path variables not correct in the script jboss-cli.sh. Right now under cygwin the paths get mixed in POSIX and Windows style. The module path (-mp param) is in POSIX style and the rest of the command is in windows style. So the startup of the org.jboss.as.cli ends up with {code} org.jboss.modules.ModuleNotFoundException: org.jboss.as.cli:main at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240) at org.jboss.modules.Main.main(Main.java:385) {code} Right now wildfly 8 beta1 has following implementation: {code:title=jboss-cli.sh|borderStyle=solid} # For Cygwin, switch paths to Windows format before running java if $cygwin; then JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"` JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"` fi {code} and it should be: {code:title=jboss-cli.sh|borderStyle=solid} # For Cygwin, switch paths to Windows format before running java if $cygwin; then JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"` JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"` JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"` fi {code} PS: I searched for similar cli issues in the issue tracker, but couldn't find any issue.