You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (Jira)" <ji...@apache.org> on 2020/01/27 10:55:00 UTC
[jira] [Updated] (GROOVY-5946) Uninformative error message (stack
trace) when adding a custom annotation
[ https://issues.apache.org/jira/browse/GROOVY-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul King updated GROOVY-5946:
------------------------------
Fix Version/s: (was: 3.x)
4.x
> Uninformative error message (stack trace) when adding a custom annotation
> -------------------------------------------------------------------------
>
> Key: GROOVY-5946
> URL: https://issues.apache.org/jira/browse/GROOVY-5946
> Project: Groovy
> Issue Type: Improvement
> Components: Compiler
> Affects Versions: 2.0.6, 2.1.0-rc-3, 2.1.0
> Environment: OSX, Gradle or IntelliJ compile or Maven eclipse compiler
> Reporter: Scott Murphy
> Priority: Major
> Fix For: 4.x
>
>
> Adding the Gaelyk annotation @Entity results in a stack trace during compilation. In addition, no informative message is given as to which groovy file caused the issue.
> At the very least, a more explicative message (not a stack trace) should be given to the user as well as informing the user which file could not be compile.
> In a more general case, any stack trace that is thrown should have a message included with it stating the offending file name.
> Example:
> {code}
> @Entity
> class Favorite {
> ÃâàÃâàDate created
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)