added a comment - - edited
To clarify - this issue is a mix of two problems :
- known limitation as it were reported here against first version of plugin - inner classes not properly handled, which does not lead to an exception, but leads to incorrect results
- exception thrown during analysis as it was reported in
SONARPLUGINS-1123, which means that project can't be analysed in general
First behaviour is acceptable for me for the moment, since we know about it, but don't know how to deal with it.
And I unsuccessfully tried to reproduce second one.
I tried with a real-world projects (CodeNarc 0.9 and GMetrics 0.4) and tried to create my own project to reproduce IllegalArgumentException, but was unable to do this in a combination of Sonar 2.12 and Sonar Groovy Plugin 0.4 : see SONARPLUGINS-597.zip, which contains Maven project with two groovy files - one with enum and another one with two classes.
So question is what I'm doing wrong and could someone provide a real-world Maven project to reproduce exception?