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.
Sometimes, when I hit ctrl-shift-F6 for "execute project", NetBeans prompts me to select the project's main class even though I had previously set it. Don't know how to reproduce reliably.
I'm experiencing this as well. I think that it happens when I change the project in the IDE. After a restart the IDE tries to load the main class from the previous project instead of the current. When you open the project settings they are completely blank, no properties at all. I have attached an ide.log which shows the problem. You can see that there is a problem while loading the project options (Line 215 in ide.log) After that you will see an exception reporting an org.openide.loaders.DataObjectNotFoundException WbManager.java could not be loaded because that was the main class from the previous project NOT the current one. The current project's main class is a JSP page if that matters.
Created attachment 7504 [details] ide.log with problem when loading project options
Another comment from Nice Max: Reproducing this behavior is straightforward: 1. Create a new project 2. Mount an existing directory 3. Create a single class with main() method 4. Add the directory to the project ("Tools"->"Add to Project") 5. Set the newly created class as project main class. 6. Execute the project - should work fine 7. Exit Netbeans 8. Restart Netbeans and execute the project again. At this point Netbeans shows the "Set Project Main Class" dialog. This happens on every newly created project. I just made a test with an existing project where NB remembers the project main class. I have created a new class and marked this one as project main class. After restarting, NB has forgotten about the new main class and starts the old one when executing the project. I think, somehow NB is unable to save its settings correctly.
*** Issue 28924 has been marked as a duplicate of this issue. ***
Marking as random since I'm not able to reproduce according to your steps.
This is the same problem like issue #26171 and it's already fixed. *** This issue has been marked as a duplicate of 26171 ***
closed