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 am not sure if I am missing something, but TOOLS/SET AS PROJECT MAIN CLASS does not work in Netbeans 3.4 to 3.5 beta. If I have a simple three class program mounted, I still have to select my main class before I run or debug. TOOLS/SET AS PROJECT MAIN CLASS eems to have no effect.
Reassigned to projects. Serious problem for new user who want to use projects. This bug should be fixed in Netbeans 3.5 release. Set main class works incorectly when the class is not in project or is removed from project. 1) isn't in project User is considering that the main class was setted. But that's not true. There is necessary at less to show warning dialog that the setting main class failed because the class is not in project. 2) the class is removed from project The class rests main class when is removed from project. There is necessary to remove main class setting.
We could discuss if 1) is even a bug. It works this way couple of releases. The action says Set As Project Main Class, but actually the class is not in the project so it cannot be set as project main class. There should be some warning dialog, but I doubt it can be fixed in release35. 2) is a bug or at least is not consistent with 1).
IMO, this is not P2, no data loss, workaround exists. John, could you please to propagate it somehow in docs and perhaps release notes. Thanks. In new projects this will be non-issue.
Proposed relnote: The IDE allows you to choose a project main class that has not been added to the project, but it does not treat the class as the main class. Solution: Right-click the file and choose Tools | Add to Project.
Sounds good.
removing RELNOTE since this seems to work in 3.6
Now irrelevant.
closed