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.
Summary: | NullPointerException at org.netbeans.modules.groovy.refactoring.rename.RenameRefactoringPlugin.isAlreadyInResult | ||
---|---|---|---|
Product: | groovy | Reporter: | Martin Janicek <mjanicek> |
Component: | Refactoring | Assignee: | Martin Janicek <mjanicek> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.3 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 195683 |
Attachments: | stacktrace |
Description
Martin Janicek
2012-11-26 09:17:59 UTC
Created attachment 128376 [details]
stacktrace
Reproducible test case: Superclass x = new Superclass() class Superclass { } ..rename refactoring on Superclass and the NPE shows up Ok, this is happening only in cases where the file name is the same as class declared inside. This is generally problem and makes groovy compiler complains about duplicate definition of the class. I'll improve the code to get rid of the exception but the refactoring won't work in this special case anyway. Fixed in: web-main #ee8e34360cd5 Integrated into 'main-golden', will be available in build *201211270002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/ee8e34360cd5 User: Martin Janicek <mjanicek@netbeans.org> Log: #222741 - NullPointerException at org.netbeans.modules.groovy.refactoring.rename.RenameRefactoringPlugin.isAlreadyInResult |