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.
[ JDK VERSION : 1.6 ] Hi I do not know wheater this is a bug or not. create a Suite for Netbeans platform , and then add a module to it you can add no module if you like. now press F6 , it raise an error about "Basic Branding information" ---------------- Created dir: E:\dev\WorkSpace\netbeans_ws\Suite\suite11\build\cluster\config\Modules run: E:\dev\FrameWorks\netbeans\harness\suite.xml:144: The following error occurred while executing this line: E:\dev\FrameWorks\netbeans\harness\run.xml:31: You must set app.name (see Branding panel in suite Properties dialog) before attempting to run an application on the NetBeans Platform. BUILD FAILED (total time: 0 seconds) --------------- (right click on suite node in project explorer->Buil->Basic Branding ,user should enable the checkbox to allow him/her to compile the suit) I think it should add those information [name and title] by default and let user to compile his fresh-created application wthout stopper.it can add those name and title by information user entered at suit creation. if you once enable that check box ,compile the suit, now if you even disable the checkbox it will compile correctly as i think it add those entry to the build files. A bug ?
There are two separate bugs here. I will leave this one open that the GUI does not warn you politely that you need to configure branding first, as it does before e.g. making a JNLP app - you have to read the error message from Ant. I also filed issue #66844.
Could be fixed together with issue #65006.
Hi as i worked with platform suite and module i find that if you made a single module and press f6 you will have same problem. i mean it will ask for branding information , *but the module has no UI* for setting branding information.
I can fix that too, to just provide a warning: you cannot use a standalone module with the bare NB Platform. Or rather you *can* build it OK, but it does not make sense to run it.
Will fix for 5.0.
Changed my mind. Easier to just arrange it so that running a non-app suite or standalone module atop the bare platform *is* permitted.
committed Up-To-Date 1.12 apisupport/harness/release/run.xml
Verified , it works in RC1