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.
NetBeans IDE Dev (Build 200610161800) 1.6.0-rc; Java HotSpot(TM) Client VM 1.6.0-rc-b99 Windows XP version 5.1 running on x86 en_US (nb); Cp1252 1) create java app with main class 2) open and close main class 3) rename project (check Also rename project folder) 4) invoke File|Open recent file -> org.openide.loaders.DataObjectNotFoundException: MasterFileObject@1e1d547[C:/Documents and Settings/Tomas Musil/My Documents/NetBeansProjects/JavaApplication15/src/javaapplication15/Main.java] at org.openide.loaders.DataObject.find(DataObject.java:469) at org.netbeans.modules.openfile.RecentFileAction.fillSubMenu(RecentFileAction.java:115) at org.netbeans.modules.openfile.RecentFileAction.popupMenuWillBecomeVisible(RecentFileAction.java:85) at javax.swing.JPopupMenu.firePopupMenuWillBecomeVisible(JPopupMenu.java:638) at javax.swing.JPopupMenu.setVisible(JPopupMenu.java:752)
unlike in issue 87311, expected behaviour is to reflect such a change and look for a file in a renamed project folder. P2 since this is one of M4 features.
After fix of 87252, no exception in thrown, file is just removed from RecentList, which is IMHO not so critical problem, consider to lower priority to P3...
This is heads-up call: I won't be able to fix this issue into M4, as the fix is really complicated, error prone and resources intensive. Current state is that moved file is deleted from recent list, regardless of whether the file was moved manually or during project rename. No exceptions. I consider current state as good enough (especially for M4) and IMHO it's not worth to fix it. Please remove the issue from M4 stoppers and consider to close as wontfix. Let me know what you think.
IMO for M4 this is good enough, but i disagree to close as wontfix.
musilt2: I respect that you don't agree with wontfix, but I'm not able to fix it. Does it make sense to have this issue opened forever? Surely no.
ok, i do understand that fixing this is overcomplicated, and probably would badly affect performance. Can be consedered as fixed the way it is now.
thank you.
verified.