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.
[NB32-38, RC4] jdk1.3, rh70 =============== This problem is serious, but I don't have exact reprodction:-( And it happens to me more then it is healthy. Description: ============ If you edit java file which is named after your public "Main" class" and this file contains also <default> "Secondary" class. Sometimes happens that after compiling and if there occures compiled errors, this file is renamed after "Secondary" class which is nonsence. I'm sorry I can give you accurate info.
I think, I have found reproduction: 1. Create class public A (in file A.java) 2. Create <default> class B (in file A.java) 3. Copy class B and paste it before class A: class B { } public class A { } 4. file A.java is renamed to B, regardless of the fact, that the public class is still "A"
Target milestone -> 3.3
Fixed in main trunk. /cvs/java/src/org/netbeans/modules/java/parser/BaseElementInfo.java,v <-- BaseElementInfo.java new revision: 1.6; previous revision: 1.5 done
*** Issue 12097 has been marked as a duplicate of this issue. ***
[dev-199] Verified
[ffj30] Verified
Resolved for 3.4.x or earlier, no new info since then -> closing.