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.
Product Version: NetBeans IDE Dev (Build 201102280001) Java: 1.6.0_24; Java HotSpot(TM) 64-Bit Server VM 19.1-b02 System: Linux version 2.6.35-25-generic running on amd64; ANSI_X3.4-1968; en_US (nb) Userdir: /home/tomas/.netbeans/dev ------------------------------------------------ - create new nbm module - clean and build - invoke Reload in target platform - it does not seem to invoke anything. Install/Reload in development IDE works. It could be probably mapped to the same goal as Run, but it currently does not work OOB neither (issue 191078)
As in bug #191078, creating standalone NBM projects with Maven is to be discouraged. Make an application project instead.
I would personally vote for removing this archetype from New project wizard, if we intend maven apisupport for apps built on top of NB platform, not for extending NB itself (standalone modules). The same for Module suite.
(In reply to comment #2) > intend maven apisupport for apps built on top of NB platform, not for > extending NB itself (standalone modules). The same for Module suite. You can certainly use maven.apisupport to develop modules for the IDE. But you should still use the Application archetype, specifying the IDE version and clusters you wish to build and test against.
sure, but question still remains - why do we keep these archetypes in new project wizard if they are not recommended to use them for development? Moreover, they do not work OOB... (issue 191078) (In reply to comment #3) > (In reply to comment #2) > > intend maven apisupport for apps built on top of NB platform, not for > > extending NB itself (standalone modules). The same for Module suite. > > You can certainly use maven.apisupport to develop modules for the IDE. But you > should still use the Application archetype, specifying the IDE version and > clusters you wish to build and test against.
They are more convenient for very quick, one-off demos.
(In reply to comment #5) > They are more convenient for very quick, one-off demos. I would suggest we just remove it from the primal archetypes list and just let the knowledgable crowd use it from the complete list in MavenProject From Archetype wizard.
in http://hg.netbeans.org/core-main/rev/fad8c401388e i've removed the suite wizard from the UI, it's been long marked as not suites for production environments