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.
I'm finding that F6 and shift-F^ no longer work in the nightly builds. Everything has been working fine up to and including the 5/26 build. After then, shift-F6 just goes "beep" on my project. F6 just loops over and over raising a "Run Project" dialog saying "com.rentec.foo.Bar wasn't found in XYZ project". When I select a class from the provided list, I get the dialog again stating that the newly selected class can't be found. I have tried removing my .netbeans, and creating a new project with the same sources, etc., but still no luck. If I make a new little "hello world" project then I find that this does run. Anyway, as I wrote, all was fine up until 5/26.
I did a little more work on trying to narrow this down. F6 and shift-F6 fail when I make a General "Java Project with Existing Sources". If I make a plain Java Application and then just copy my existing source into the project directory, then all works as expected.
I am using the newest q-build and have created half a dozen "Java projects with existing sources." Everything worked fine until I closed the IDE and restarted it. After that NB42 somehow lost the package information for all packages. What I mean by this is: when I select a file in the project tree it displays the tooltip "Invalid package declaration". When I generate a new file inside a package the package statement is missing, as if it had been created in the default package. The missing package information is also the reason why Shift-F6, F9 and Ctrl-Shift-F5 stopped working. It happens with Tiger and Mustang (b39) and renders the qbuild unusable, at least for this type of project. Thanks, Georg
Were you doing any customizations of those projects? Stange, did your projects also lost package information? I cannot reproduce the problem, would be good if you could provide some step-by-step testcase on how to reproduce it.
This is a consequence of issue #60297. *** This issue has been marked as a duplicate of 60297 ***