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.

Bug 231477 - Right-click "Set as Main Project" does not initially appear in the list of possible commands.
Summary: Right-click "Set as Main Project" does not initially appear in the list of po...
Status: VERIFIED DUPLICATE of bug 166780
Alias: None
Product: javafx
Classification: Unclassified
Component: Project (show other bugs)
Version: 7.4
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Petr Somol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-18 22:03 UTC by Lou Dasaro
Modified: 2013-12-18 20:13 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lou Dasaro 2013-06-18 22:03:08 UTC 
I have a number of JavaFX projects. Installed Netbeans 7.4 Beta. (Tried with several different builds)

Initially, no project is selected as the "Main Project"

Right-clicked on a project, but "Set as Main Project" does not appear in the list of possible commands.

Only once you select a "Main Project" from the Run->Set Main Project dropdown does Set or UnSet Main Project appear as an option when Right-clicking a project.

Error occurred using base IDE (Java SE) as well as Jave EE dist.

It's an annoyance, not a showstopper for me.
Comment 1 Petr Somol 2013-06-20 12:07:40 UTC 
This is by design, see Issue #166780. It had been decided some time ago not to promote "Set as Main" initially and switch the functionality on only for those users that demand it and who access it from main menu. When using the IDE without "Set as Main", the currently selected project is always the one that is built/run etc.

*** This bug has been marked as a duplicate of bug 166780 ***
Comment 2 Lou Dasaro 2013-06-20 16:17:48 UTC 
IMHO, the way it's handled now is counter-intuitive and appears to have been decided without much (if any) user input. However, there seems to have been enough internal "decisioning" conversations, and if you don't receive many bug reports regarding this "feature", then I guess it was rightly decided from a management perspective!