Bugzilla – Full Text Bug Listing
| Summary: | NPE happens in Java Builder with enabled annotation-based analysis and groovy | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Sergey Bogatyrev <sergebogatyrjov> | ||||
| Component: | Core | Assignee: | Stephan Herrmann <stephan.herrmann> | ||||
| Status: | CLOSED NOT_ECLIPSE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | stephan.herrmann | ||||
| Version: | 4.12 | ||||||
| Target Milestone: | 4.13 M3 | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Can you reproduce this also *without* the groovy plugin? You might be aware that they ship their own patched variant of org.eclipse.jdt.core, so if it only happens with that plugin you should first report it to them, even if the exception happens in org.eclipse.jdt.core... I can't reproduce it without groovy. So, it looks like I should submit it to plugin developers. (In reply to Sergey Bogatyrev from comment #2) > I can't reproduce it without groovy. So, it looks like I should submit it to > plugin developers. Thanks. Feel free to re-open, if the developers of the Groovy plugin conclude that the bug is in JDT indeed. Submitted to groovy-eclipse: https://github.com/groovy/groovy-eclipse/issues/931 |
Created attachment 279486 [details] Error event details Happens when Groovy plugin installed and annotation-based null analysis enabled. Disabling of annotation-based null analysis everything fixes errors. I am building a java project including multiple modules. Groovy is used for testing. Tests are based on Spock framework. In these tests we have non-standard naming, something like this: def "run scenario and perform checks"() { ... } Internal compiler error appearing in "Problems" never relates to groovy code. Usually I can see 2 or 3 errors relating java files. For the same set of modules I get the same errors. Groovy plugin: Groovy Development Tools 3.5.0.SNAPSHOT (installed from marketplace) The error was discovered long time ago, and can be reproduced with earlier versions of eclipse and groovy plugin.