Currently EAP 6.2.x has broken cygwin support. To fix and bring in sync with upstream which is already fixed:
> diff --git a/build/src/main/resources/bin/jboss-cli.sh b/build/src/main/resources/bi
> index b971615..969151f 100755
> --- a/build/src/main/resources/bin/jboss-cli.sh
> +++ b/build/src/main/resources/bin/jboss-cli.sh
> @@ -61,6 +61,7 @@ fi
> if $cygwin; then
> JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
> JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
> + JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
> if $darwin ; then
It is actually WFLY-2523 that fixed it upstream and this is the upstream commit:
Marking for inclusion in 6.2.1 release notes documentation.
Changed from Bug Fix to Known Issue to fix Bug 1097087
Refactored release note text for this as a Known Issue (ER4 fixes will not be picked up in the 6.3.0 Beta release)
Original note included here for use at 6.3.0 GA:
Problems were encountered using earlier versions of JBoss EAP 6 in Cygwin. Differences in the POSIX and Microsoft Windows pathing implementations caused the path variables in the +jboss-cli.sh+ shell script to fail to function as expected. A refinement in the +jboss-cli.sh+ shell script now allows the variables to operate as expected in Cygwin environments.
Just spotted this, don't believe it should be dev acked - we have already rejected another BZ as we have no solution for prompting for a password without echoing on cygwin.
Overall I believe cygwin support should currently be classed as an RFE.