Though I'm not getting the "empty console window". I am getting other unpredictable and cryptic errors running some commands (like "grails war" for deploying app to TcServer or "run-app", or "compile" when installing plugins etc.
These weird behaviors go away when I reinstall my JDK. So it seems still a good idea to have this check.
I don't think now, it is urgent enough to put this into 2.5.2. It would seem this issue doesn't affect many users because:
- most users would have a JDK installed
- if no JDK is installed, the user will already get warned by maven that they need to have a JDK (but is true they might choose to ignore the warning if they aren't using maven).