Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0
-
Fix Version/s: 1.1-rc-2
-
Component/s: None
-
Labels:None
-
Environment:all
-
Number of attachments :
Description
To avoid frightening new users of Groovy, executing scripts should not (by default) result in a Java stack trace that indicates where within the Groovy parser processing stopped.
There should be a way to enable output of stack traces for developers of Groovy though.
Issue Links
- is depended upon by
-
GROOVY-760
improve error reporting
-
The initial drop of this is in place in CVS and for beta-4, primarily as it affects the FileSystemCompiler (groovyc). Work continues on a parser overhaul, by the end of which this bug should be closeable.