I think I already fixed this issue, which is a duplicate of this one:
It is a problem with certain characters getting included in the name of generated launch configurations to launch grails commands.
However, it is possible that more clones of the bug are lying in wait, since the code involved in launching commands appears to have been copied in a number of places and I just spotted one other place where the proper sanitation procedure had not been applied for the launchconfig name. (And of course I will fix that .
Assuming you ran it via the grails command popup, I think it should already have been fixed (If you could please try out the latest snapshot from the update site and confirm this)
However if you still have issues, I'll need some more info from you on precisely how you ran the command (as I said, we seem to have some copies of the code in question that are used under different circumstances, so I need precise details to reproduce).
I'll leave this issue open for a bit longer until I hear back from you.