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.
When renaming a class, the old <filename>.class files should be deleted. I ran into a frustrating problem where I had a <ClassName>Test.java, which I renamed because I was going to create a JUnit test which would have the same name. The JUnit test, being in the same package (but different directory) failed with "No tests found in <ClassName>Test". It took me awhile to figure out that there was still and old <ClassName>Test.class laying around in the build/classes directory. My first thought was that something was wrong with the JUnit execution, and others will likely run into the same problem.
Not sure, what is the right module for this issue. Anyway, refactoring just does DataObject.rename(). Project system takes care of .class files. Can you evaluate this issue? Thanks
The clean up after refactoring should be done by refactoring itself, otherwise it would be necessary for all project types to depend on the refactoring module.
This should be handled probably in JDO.handleRename()
The question is if we want to do it at all, the user is able to do the real clean (probably WANTFIX)
I agree with Tomas. IDE will never ensure, that all classes are up-to-date unless user do clean-build. We are sorry, but this issue is WONTFIX.
*** Issue 65981 has been marked as a duplicate of this issue. ***
*** Issue 67550 has been marked as a duplicate of this issue. ***