Cygwin: Grails 2.0.0 - Scripts not accepting user input

I am also seeing this problem on Cygwin on Win7. Specifically, using the "Cygwin Terminal" provided by a brand new install of Cygwin (rather than older Cygwin terminal emulator approaches - though I haven't tried them), I can type grails to go into interactive mode, but then anything I type is ignored and when I give up and ctrl-C to escape grails, it then runs the text I typed as the command prompt. So something's not hooked up right. This is indeed a bit of a problem for Windows developers, though I can workaround it by using a normal Windows cmd prompt.

Does this problem occur with the 2.0 release? (the original issue was filed against 2.0-RC1)

Yes, this is still a problem as of release 2.0.0

In fact it's a show stopper for me in a locked down, corporate environment, within a major UK retailer.
Cmd Window is disabled, so I need to use cygwin to drive the command line.
The MSDOS prompt is available and allows me to run the scripts and enter input, but it's unusably clunky for day to day use.

I have dropped back to 1.3.7 for moment.

Does anyone know if STS uses Cmd Window as a background process to the IDE when running commnad lines, or is there something more sophisticated going on under the hood... was wondering if that might be another workaround for me?

Could be related to http://softwaremavens.blogspot.com/2009/10/cgwin-interpretersjline-carriage-return.html

Could someone try run the grails command inside cygwin with:

grails -Djline.terminal=jline.UnixTerminal

Below is output on WinXP SP3.

Interestingly, I have managed to install STS 2.9.0.M2 here, download grails support and grails 2.0.0 inside STS and I can create a simple domain and run it - however, I get the same RegCreateKeyEx error on stderr.

bash-3.2$ which grails
/cygdrive/g/GENERAL/devenv/grails/grails-2.0.0/bin/grails
bash-3.2$ ls
application.properties grails-app lib scripts src target test web-app
bash-3.2$ grails -Djline.terminal=jline.UnixTerminal
cygpath: unknown option – j

I installed Cygwin myself and if I use the jline.UnixTerminal parameter then user input works fine:

Graeme Rocher@WIN-MUKKPM3Q2BP ~
$ /cygdrive/c/java/grails-core/bin/grails.bat -Djline.terminal=jline.UnixTerminal

| Loading Grails 2.0.1.BUILD-SNAPSHOT
| Configuring classpath
| Enter a script name to run. Use TAB for completion:
grails> list-plugins
list-plugins
| Environment set to development
| Environment set to development.
| Environment set to development..
| Environment set to development...
| Environment set to development....
| Environment set to development.....
You do not have any plugins installed.

To find more info about plugin type 'grails plugin-info [NAME]'

To install type 'grails install-plugin [NAME] [VERSION]'

For further info visit http://grails.org/Plugins

grails>

lowering priority since there is a workaround

I've just had an AHA! moment regarding Grails on Cygwin on Windows - which I will share and hope it helps others...

I've been typing [b]grails[/b] because I thought that Cygwin would do the right thing and run the *nix commands on top of windows. I tried the command line options suggested but they don't make things work.
<code>
bash-3.2$ grails -Djline.terminal=jline.UnixTerminal
cygpath: unknown option – j

bash-3.2$ list-plugins
bash: list-plugins: command not found
</code>

I spotted that Graeme just typed [b]grails.bat[/b] and this behaves differently...
<code>
bash-3.2$ grails.bat

bash-3.2$ list-plugins
bash: list-plugins: command not found
</code>

However, it still doesn't work until you add the command line options...
<code>
bash-3.2$ grails.bat -Djline.terminal=jline.UnixTerminal

To find more info about plugin type 'grails plugin-info [NAME]'

To install type 'grails install-plugin [NAME] [VERSION]'

For further info visit http://grails.org/Plugins

grails>
</code>

I presume the intention is still to fix [b]grails[/b] and not force use of [b]grails.bat[/b] ?

In the meantime I have managed to get STS 2.9.0.M2 up and running on both my personal Win7 laptop and corporate WinXP PC... so think I will try that route for a while...

Gordon

I fought this one for a couple of hours. Here is the only way I got it to run. Various symptoms included: java.lang.reflect.InvocationTargetException Caused by: java.lang.IllegalAccessError (this was a bad $CLASSPATH), the grails console hanging on any input (using grails or grails.bat instead of grails.bat -Djline.terminal=jline.UnixTerminal), probably missing a couple of others.

$ uname -a
CYGWIN_NT-6.2-WOW64 mj1 1.7.17(0.262/5/3) 2012-10-19 14:39 i686 Cygwin
$ export GRAILS_HOME=C:\\cygwin\\opt
grails-2.2.0
$ export JAVA_HOME=C:\\cygwin\\usr\\local\\java\\jdk64
jdk1.7.0_13
$ /opt/grails-2.2.0/bin/grails.bat -Djline.terminal=jline.UnixTerminal

To find more info about plugin type 'grails plugin-info [NAME]'

To install type 'grails install-plugin [NAME] [VERSION]'

For further info visit http://grails.org/Plugins

grails>

It looks like a bunch of work has been done in 'grails' to work with cygwin. I think this is the best way to go (never used a .bat in cygwin). But using 'grails' I could never get around the following error:

$ /opt/grails-2.2.0/bin/grails
cygpath: can't convert empty path

...hangs

I think I have an answer! I've had a problem with Grails 2.0 since inception. Additionally I've had a problem with any Java/Groovy apps that used System.console since System.console returns null when running inside the standard Cygwin bash shell, mrxvt, rxvt, xterm, etc.

Today I discovered ConEmu
http://code.google.com/p/conemu-maximus5/

I installed the 64 bit version. I created a new tab with the following configuration
Shell command: c:\cygwin\bin\bash.exe -l

(in fact, I changed the default shell to be this)

Now System.console doesn't return null. The grails interactive mode seems to behave correctly, writing the various startup details to a single line and tab completions working correctly.

FWIW: I am using Grails 2.2.0 and Groovy 1.8.8.