Bugzilla – Full Text Bug Listing
| Summary: | Refactoring: NPE while renaming local variable | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Dmitry Vyazelenko <vyazelenko> | ||||
| Component: | Core | Assignee: | Stephan Herrmann <stephan.herrmann> | ||||
| Status: | VERIFIED WORKSFORME | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | amj87.iitr, daniel_megert, manoj.palat, markus.kell.r, Olivier_Thomann, remy.suen, srikanth_sankaran, stephan.herrmann | ||||
| Version: | 3.7.1 | ||||||
| Target Milestone: | 4.14 M1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Dmitry Vyazelenko
Created attachment 205248 [details]
Full stacktrace of the error
Stacktrace added.
Java tooling bugs go to JDT, not Platform IDE. *** This bug has been marked as a duplicate of bug 348024 *** OK, I see that the bug was marked as duplicate of <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=348024">bug 348024</a>. However I do not agree that it can be closed because I have 3.7.1 Eclipse version in which bug is reproducible. And as far I understood the fix was suppose to be delivered as part of 3.7.1 RC2?! (In reply to comment #4) > OK, I see that the bug was marked as duplicate of <a > href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=348024">bug 348024</a>. > However I do not agree that it can be closed because I have 3.7.1 Eclipse > version in which bug is reproducible. And as far I understood the fix was > suppose to be delivered as part of 3.7.1 RC2?! Yes, the fix for bug 348024 is in 3.7.1. To understand similarity/difference to that bug, can you please tell us whether there's also a file package-info.java involved in your case? Can you share an example program where the exception can be reproduced? Yes, the package containing class in which local variable rename fails also contains package-info.java file. Unfortunately I was not able to reproduce issue with sample project. The error occurs only on closed source project. I tried to reproduce with a simple case with a package-info.java file, but works ok. Dmitry, can you extract the method into another one, omitting much of your code except the local variable on which ur'e using the refactoring? If you can still reproduce, then submitting that testcase here will help us and make sure you don't cause any IP issues. Thanks! Ping. We cannot do much here without a reproducible example. Dmitry, have you had chance to try out Ayush's suggestion from comment#7 ? This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. We don't have sufficient information for investigation. Verified for Eclipse Version: 2019-12 (4.14) M1 with Build id: I20191008-1800 |