This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 262826 - AssertionError: Expecting GroovyParseResult, but have null
Summary: AssertionError: Expecting GroovyParseResult, but have null
Status: NEW
Alias: None
Product: groovy
Classification: Unclassified
Component: Editor (show other bugs)
Version: 8.2
Hardware: All All
: P3 normal (vote)
Assignee: bruno.flavio
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-15 13:19 UTC by FrantaM
Modified: 2016-07-19 11:15 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 225257

Attachments
stacktrace (4.24 KB, text/plain)
2016-07-15 13:19 UTC, FrantaM 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description FrantaM 2016-07-15 13:19:17 UTC 
Build: NetBeans IDE Dev (Build nbms-and-javadoc-521-on-20160622)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.66-b18, Java(TM) SE Runtime Environment, 1.8.0_66-b18
OS: Windows 10

User Comments:
FrantaM: ctrl+shift+i in build.gradle




Stacktrace: 
java.lang.AssertionError: Expecting GroovyParseResult, but have null
   at org.netbeans.modules.groovy.editor.api.ASTUtils.getParseResult(ASTUtils.java:100)
   at org.netbeans.modules.groovy.editor.actions.FixImportsAction$CollectMissingImportsTask.run(FixImportsAction.java:118)
   at org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:609)
   at org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:153)
   at org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:137)
   at org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:204)
Comment 1 FrantaM 2016-07-15 13:19:18 UTC 
Created attachment 160404 [details]
stacktrace
Comment 2 bruno.flavio 2016-07-19 11:09:21 UTC 
Hello,

Thank you for submitting this bug report.

Although I was unable to reproduce the issue with a clean install, it does occur when the Gradle Support plugin is installed. Is this your case as well?

Thanks,
Bruno.
Comment 3 FrantaM 2016-07-19 11:15:34 UTC 
yes