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 196105 - Reload in Target Platform not available in deprecated "suites"
Summary: Reload in Target Platform not available in deprecated "suites"
Status: NEW
Alias: None
Product: apisupport
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.0
Hardware: PC Linux
: P4 normal (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-28 14:53 UTC by Tomas Danek
Modified: 2012-10-31 15:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Danek 2011-02-28 14:53:44 UTC
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)
Comment 1 Jesse Glick 2011-02-28 19:40:45 UTC
As in bug #191078, creating standalone NBM projects with Maven is to be discouraged. Make an application project instead.
Comment 2 Tomas Danek 2011-02-28 21:26:56 UTC
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.
Comment 3 Jesse Glick 2011-02-28 23:23:04 UTC
(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.
Comment 4 Tomas Danek 2011-03-01 10:39:34 UTC
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.
Comment 5 Jesse Glick 2011-03-01 15:29:41 UTC
They are more convenient for very quick, one-off demos.
Comment 6 Milos Kleint 2012-10-22 07:15:20 UTC
(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.
Comment 7 Milos Kleint 2012-10-31 15:05:15 UTC
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