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.
After I create a Module Suite on Solaris, I can see a Build Installers item in the project's right-click menu. I also see an Installer page in the project's Project Properties dialog. I do not see these UI elements if I create a Module Suite project on Mac OS X. It appears that other folks do not see these UI elements on Windows: http://stackoverflow.com/questions/3350368/netbeans-installer If nothing else, we may want to add more verbage about the limitation of the feature to http://wiki.netbeans.org/NewAndNoteworthy69#Installer_generation_support_for_RCP.
Which bundle are you using? All/JavaSE/Java/...? Does the issue go away after you activate "NetBeans Plugin Development" in Tools->Plugins, "Installed" tab (detailed view)?
(In reply to comment #1) > Which bundle are you using? All/JavaSE/Java/...? netbeans-6.9-ml-java-macosx.dmg > > Does the issue go away after you activate "NetBeans Plugin Development" in > Tools->Plugins, "Installed" tab (detailed view)? the menu item appears after activating that module. So, I guess the bug is the fact that the module 'NetBeans Plugin Development' does not activate when the user creates a 'NetBeans Modules->Module', 'NetBeans Modules->Module Suite', or a 'NetBeans Module->NetBeans Platform Application' project in the IDE with NB 6.9.
Thanks, I'll look into that.
Vince, can I ask you to attach messages.log ?
No problem. I did a bit more work to narrow down what happens. If I: start 6.9 with a new userdir, then create a module suite project, then look at the activated plugins... NetBeans Plugin Development is activated. If I: start 6.9 with a new userdir, then create an ant based Java Class Library project, then create a module suite project, then look at the activated plugins... NetBeans Plugin Development is activated.
Created attachment 101083 [details] messages.log This log is from the second case outlined in my previous comment.
Jarda, could you please look into this (likely ergonomics) issue? > the bug is the fact that the module 'NetBeans Plugin Development' does not activate when the user creates a 'NetBeans Modules->Module', 'NetBeans Modules->Module Suite', or a 'NetBeans Module->NetBeans Platform Application' project in the IDE with NB 6.9.
Correction... (In reply to comment #5) > No problem. > > I did a bit more work to narrow down what happens. > > If I: > start 6.9 with a new userdir, then > create a module suite project, then > look at the activated plugins... > NetBeans Plugin Development is activated. > > If I: > start 6.9 with a new userdir, then > create an ant based Java Class Library project, then > create a module suite project, then > look at the activated plugins... > NetBeans Plugin Development is NOT activated.
ergonomics#7b98f75ef9bd
The cure looks worse than the disease. Now the Java SE feature turns on the NetBeans Module Development feature. This is backwards! Please find some better way of fixing this issue.
Integrated into 'main-golden', will be available in build *201008210001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/7b98f75ef9bd User: Jaroslav Tulach <jtulach@netbeans.org> Log: #189026: Explicitly require apisupport.kit from java.kit
As has been agreed during 6.7 implementation of Ergonomics, it is important to reuse existing distributions: http://wiki.netbeans.org/FitnessForever#Reuse_Existing_Distributions Until the whole organization agrees on that this is no longer our goal, it is quite natural to enable NetBeans Module Development together with Java SE. There is no NetBeans Module Development distribution, it is included in Java SE. In the context of above, I am making this bug fixed. Menu item 'Build Installers' is no longer missing. The request to separate NetBeans Module Development is tracked as separate issue 168618 (and has not gained much corporate support so far).
(In reply to comment #12) > it is quite natural to enable NetBeans Module Development together with Java SE. The issue is that it is now *impossible* to disable NBMD when Java SE is enabled. That is an unacceptable condition, regardless of which components happen to be distributed in a package.
That is a different bug. Report it and make it P4.