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 204966 - Project Template wizard hits a dead-end for maven based NBM projects
Summary: Project Template wizard hits a dead-end for maven based NBM projects
Status: RESOLVED INVALID
Alias: None
Product: apisupport
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.1
Hardware: PC Solaris
: P2 normal (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-11 00:44 UTC by Vince Kraemer
Modified: 2011-11-11 15:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vince Kraemer 2011-11-11 00:44:15 UTC 
Steps to reproduce.

Pulled the most recent sources for NB 7.1 and built it. (I have no local changes, in play or unpushed)

I started the built IDE with the current Mac OS Java runtime (1.6.0_26).

I created a File->New Project... category: Maven projects: NetBeans Module project.

I created an ant-based Web App project.

I used File->New->Other... category: NB Module Devel type: Project Template to get to the first page of the wizard

I selected my web app project on the second page of the wizard.

When I get to the third page of the wizard, I see the message 'The NetBeans platform is missing required modules.'

I tried a bunch of different values in the 'Template name', 'Display name' and Category fields of the wizard... but none of them seemed to be the necessary incantation to enable the wizard's Finish button.

I did double check the ant based NetBeans Module project's behavior.

It seemed to work correctly.
Comment 1 Jesse Glick 2011-11-11 15:58:50 UTC 
If you use a standalone module, you might need to build & run it first in order to create a temporary "platform" in which the IDE can find API modules. I tried it just now and it worked fine, perhaps because relevant modules were already in my local repository.

Generally speaking, development with standalone modules and "suites" using Maven is not fully supported, which is why it is not recommended for production code in the New Project wizard. For example, running & functional testing is impossible without passing in an external NetBeans installation path.

The preferred setup is an "application", which then obtains all its dependencies from the Maven repository in the normal way. The default application archetype includes only the platform cluster, so if you want to run the Project Template wizard you would need to also include at least parts of the ide cluster. (To be able to test this project template you would also want to include the java, enterprise, and I guess websvccommon clusters, though see bug #204995.)