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.
Hi, After importing an NB 136 project into 142, I want to open the project and after that, I get firstly the question if I want to update the parser-DB, I chose 'No' and then during opening I get a whole list of exceptions (see attached file). When clicking 'Ok' on the window that lists the exceptions per module, I get that question if I want to update the parser-DB again. Iwan
Created attachment 766 [details] Screenshot of the error-window mentioned in this issue
Assigning to David to check why I will have closed the bug.
In my opinions you do not have installed some modules from your previous IDE in latest build. Especially I mean JINI and innertesters or apisupport. If true, then I do not think this is a bug.
I didn't have anything installed. I installed Dev build 142 from scratch, imported the projects from my Dev 136 and that's it. If this is a problem because there is something that should be there, but isn't, I would surely expect a message telling me that something is missing. I had the same error with NB 3.2 beta tag 1, which means that the distribution is not compatible with the dev-builds or the 3.1 version, as I had the same problem with my 3.1 projects after importing them. Iwan
Apparently jini, apisupport, and innertesters were installed in the old project, and are not now available--so Jarda is right, the projects module is simply not able to load them (with current settings storage design). But the dialog it shows should explain more clearly that this is the probable reason why it had trouble loading these things, so users are not troubled by it.
The description and UI of the dialog should be both improved. Marking as duplicate of previously reported bug concerning this dialog. If you disagree and think that it is not just matter of the discussed dialog, please reopen. *** This issue has been marked as a duplicate of 9989 ***
Resolved for 3.3.x or earlier, no new info since then -> closing.
Resolved for 3.4.x or earlier, no new info since then -> closing.