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've follow the instructions in the file netbeans/harness/README (nbplatform-bin-5.0beta), section "USING A RELATIVE PATH FOR THE PLATFORM WITH A MODULE SUITE". My <mysuite>/nbproject/platform.properties is: suite.dir=${basedir} netbeans.dest.dir=${suite.dir}/../nb_sources/nbbuild/netbeans harness.dir=${netbeans.dest.dir}/harness All work fine (great work!!), but if I open the suite module in Netbeans IDE 5.0beta for developing it, when I choose the Project Properties (from popup menu) in the module suite node (in the Projects view) I've got this exception: java.lang.NullPointerException at org.netbeans.modules.apisupport.project.suite.BrandingSupport.init(BrandingSupport.java:335) at org.netbeans.modules.apisupport.project.suite.BrandingSupport.getInstance(BrandingSupport.java:60) at org.netbeans.modules.apisupport.project.ui.customizer.BasicBrandingModel.getBranding(BasicBrandingModel.java:230) at org.netbeans.modules.apisupport.project.ui.customizer.BasicBrandingModel.initBundleKeys(BasicBrandingModel.java:289) at org.netbeans.modules.apisupport.project.ui.customizer.BasicBrandingModel.init(BasicBrandingModel.java:240) at org.netbeans.modules.apisupport.project.ui.customizer.BasicBrandingModel.<init>(BasicBrandingModel.java:96) at org.netbeans.modules.apisupport.project.ui.customizer.SuiteProperties.<init>(SuiteProperties.java:75) at org.netbeans.modules.apisupport.project.ui.customizer.SuiteCustomizer.prepareData(SuiteCustomizer.java:63) at org.netbeans.modules.apisupport.project.ui.customizer.BasicCustomizer.showCustomizer(BasicCustomizer.java:103) at org.netbeans.modules.apisupport.project.ui.customizer.BasicCustomizer.showCustomizer(BasicCustomizer.java:94) at org.netbeans.modules.apisupport.project.ui.customizer.BasicCustomizer.showCustomizer(BasicCustomizer.java:89) at org.netbeans.modules.project.ui.actions.CustomizeProject.actionPerformed(CustomizeProject.java:70) at org.netbeans.modules.project.ui.actions.LookupSensitiveAction.actionPerformed(LookupSensitiveAction.java:100) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786) at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258) at javax.swing.AbstractButton.doClick(AbstractButton.java:289) at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1113) at javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(BasicMenuItemUI.java:943) at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231) at java.awt.Component.processMouseEvent(Component.java:5100) at java.awt.Component.processEvent(Component.java:4897) at java.awt.Container.processEvent(Container.java:1569) at java.awt.Component.dispatchEventImpl(Component.java:3615) at java.awt.Container.dispatchEventImpl(Container.java:1627) at java.awt.Component.dispatchEvent(Component.java:3477) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128) at java.awt.Container.dispatchEventImpl(Container.java:1613) at java.awt.Window.dispatchEventImpl(Window.java:1606) at java.awt.Component.dispatchEvent(Component.java:3477) [catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:456) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137) at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
A workaround for make the suite Project Properties dialog available is to insert in <mysuite>/nbproject/platform.properties this line: nbplatform.active=default But in the README file I read: "The platform.properties should *not* define 'nbplatform.active' in this case."
Right... the harness is fine, but SuiteProject.getActivePlatform assumes nbplatform.active has been defined. It should actually be using ${netbeans.dest.dir} to find the platform. BTW your workaround may prevent exceptions but might cause other lesser problems in e.g. code completion (I'm not sure).
I follow the same instruction, but I did an ant clean in the suite directory instead. This is the error I got: BUILD FAILED C:\cygwin\home\nam\coke\jse_all\libs\build.xml:7: The following error occurred while executing this line: C:\cygwin\home\nam\coke\jse_all\libs\nbproject\build-impl.xml:19: You must define 'nbplatform.${nbplatform.active}.harness.dir'
nnguyen - then I guess you did not set things up correctly. Reread the README and check for things you might have missed, and of course use -v and -d to get diagnostics from Ant. This bug report is that the harness *is* working correctly but the IDE's development-time support has a problem.
Well, my guess I just want to report another symptom in another user case that I think came from the same cause that ${nbplatform.active} is not set. Sorry that it does not contribute any value.
I am making this P2 per rmatous request in issue 66218
P2 as Jarda wished and forgot to raise.
Ought to be fixed now - this problem at least. File separate issues with steps to reproduce for anything else you encounter. committed Up-To-Date 1.22 apisupport/project/src/org/netbeans/modules/apisupport/project/suite/SuiteProject.java
verified in nb50 rc1