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 199920 - Renaming case of a java class makes class unreachable
Summary: Renaming case of a java class makes class unreachable
Status: RESOLVED DUPLICATE of bug 198565
Alias: None
Product: java
Classification: Unclassified
Component: Refactoring (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: Jan Becicka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-06 13:40 UTC by tomzi
Modified: 2011-10-25 12:51 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tomzi 2011-07-06 13:40:23 UTC
Steps:
.) I create a class eg Myclass.java under 'Source Packages' and another class MyOtherClass.java under 'Test Packages' which creates an instance of Myclass.
,) I refactor Myclass to MyClass
-> Refactoring worked just fine, however suddenly Netbeans does not recognize MyClass anymore (Error: 'Cannot find symbol ... MyClass')

.) I refactor this class back again to Myclass 
-> Myclass is perfectly renamed back again
-> In MyOtherClass however I still have my old reference to MyClass

I also sometime got an error with this second step saying ?!Class or Object already exist...?! or something similar

I am working with maven and:

Product Version = NetBeans IDE Dev (Build 201106041000)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.6.0_25
Runtime = Java HotSpot(TM) 64-Bit Server VM 20.0-b11
Comment 1 Jan Becicka 2011-10-17 09:05:12 UTC
Cannot reproduce on Mac. Maybe Windows specific (Windows file system is not case sensitive)
Comment 2 Jan Lahoda 2011-10-17 09:09:08 UTC
Possibly a duplicate of bug #198565? Could you please try on 7.0.1? Thanks.
Comment 3 Jan Becicka 2011-10-21 14:14:23 UTC
Jirko, can you reproduce it on Windows?
Comment 4 Jan Becicka 2011-10-25 12:51:28 UTC

*** This bug has been marked as a duplicate of bug 198565 ***