How to "not" to fail groovy scripts inside builds

[patric]

Hi,

first: congrats. Nice piece of work - I was waiting on something like
that already, just didn't had the time. Thanks for that.

A first test shows to shortcomings currently:
- everything found is an error and stops compiling completely (which
you adressed with your first question. Sorry, don't know it either)
- within ant build with embedded groovy scripts (taskdef'd), I cannot
add the annotations easily. It will fail upon "dynamic_field_access"
for ant, properties and target, the main interface to ant in this
case.

tia,

Patric

[Kyle]

Hi Patric,

Thanks for trying it out and giving feedback :)

- Yea, I've been trying to figure out how to issue a warning instead
of an error for a while now. I asked on Stackoverflow.com and the
Groovy mailing list, but didn't get any answers.

- I'll see if I can come up with a way to turn off checking for
certain classes/methods without using annotations. In the mean time,
try turning off the dynamic_field_access check completely by setting
"dynamic_field_access = off" in the GroovyLintSettings.groovy file,
and making sure GroovyLintSettings.groovy is on your classpath.