[#GROOVY-139] user vs. developer error messages - filtering stack traces

groovy

user vs. developer error messages - filtering stack traces

Created: 19/Jan/04 01:00 PM Updated: 22/Nov/07 05:26 AM

Component/s:

None

Affects Version/s:

1.0

Fix Version/s:

1.1-rc-2

Time Tracking:

Not Specified

Environment:

all

Issue Links:

dependent

This issue is depended upon by:

~~GROOVY-760~~ improve error reporting

Description

« Hide

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.

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

Chris Poirier added a comment - 03/Mar/04 02:31 PM

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.

[ Permalink | « Hide ]

Chris Poirier added a comment - 05/Mar/04 01:24 PM

The latest CVS code now contains:

further parser recovery points; and
error reporting in the Groovyc Ant task.

[ Permalink | « Hide ]

Jochen Theodorou added a comment - 10/Jun/05 07:41 AM

things where better in beta-10 and after switching to the jsr compiler there were many new stacktraces. But I think JSR-02 will be much better here

[ Permalink | « Hide ]

Paul King added a comment - 18/Jun/07 03:49 AM

Is this supported now with the -d switch or is something more expected?

[ Permalink | « Hide ]

Paul King added a comment - 15/Oct/07 03:09 AM

No further feedback, assuming current -d is all that is required.