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.
Issue: A participant executes a class using its contextual menu, after closing the profiles dialog open by the run action. He doesn't set up the profile, just closes the dialog. Analysis: The barrier to running a project is too high. The concept of profiles is not helpful or necessary at the point and should only be introduced when there is need. Recommendation(s): See below.
Issue: A participant closes the profiles dialog because he thinks he doesn't need it for execution. Analysis: Profiles problem - the concept does not have an obvious connection with running the project. Recommendation(s): The profile may not be necessary for many cases where the user wants to run a project -removing it from the direct path would reduce the number of steps to running a project. In simple cases with only one runnable class the IDE should run the class without extra input from the user. When creating a new class that is runnable the IDE should keep track and perhaps offer the a choice when Run project is later selected. More work needs to go into the profile issue.
Issue: A participant invokes the run action from project's popup menu, but it displays the profiles dialog even if a profile exists. It is because non of the profiles is active (default). Analysis: UI Bug Recommendation(s): When only one profile exists it should be the default.
Issue: A participant executed the active project using main menu, but it runs the old profile pointing to incorrect main class, which has been deleted. The participant doesn't know where is the problem. The output just says "No class def found error." Analysis: UI Bug Recommendation(s): When the class an execution profile depends on is deleted the the profile should be deactivated as well.
"When creating a new class that is runnable the IDE should keep track" -- this seems promising for pure-java project (or generally should be applied when there's only one profile type). I think typical production environment with stuff as JUnit (tests), JAR execution, etc should be considered for the overall picture. Also consider possible inconsistencies of IDE keeping track of classes created within the IDE itself vs. source files (also runnable) created externally and added to the project or checked out from VCS.
the desired behavior has been spec'd
As described in http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the current work on projects prototype has been stopped. Marking issue as VERIFIED --->
---> CLOSED