Sort error messages by line number

[GoogleCodeExporter]

Currently error messages are reported in the order they appear in byte code. 
Unfortunaetly with synthetic methods like used for closures or access$X stuff, 
the methods may come later in byte code, so those synthetics are listed after 
other failures, although line number is lower.

The fix would be to buffer the error messages and sort them by line number 
before output. This would also allow to make them accessible in a more 
structured way from code.

Original issue reported on code.google.com by uwe.h.schindler on 27 Sep 2013 at 9:24

[GoogleCodeExporter]

Original comment by uwe.h.schindler on 27 Sep 2013 at 9:24

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

This issue is a prerequisite for issue #34. Issue #34 will just add final 
buffered output and sorting if the suppressing annotation is not visible.

Original comment by uwe.h.schindler on 25 Dec 2014 at 12:33

[GoogleCodeExporter]

Committed in r346:
Capture synthetic "lambda$" methods and keep them in the declaring method while 
outputting forbidden violations: Introduce groupId for each code block, map 
groupId of lambdas back to their declaring method (where the corresponding INDY 
was seen)

Before this commit there were more refactorings in the checker code to have 
more classes. Also the forbidden violations were buffered (but not yet sorted), 
before they were printed.

Original comment by uwe.h.schindler on 26 Dec 2014 at 12:38

• Changed state: Committed