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.
Build: NetBeans IDE Dev (Build 071218) VM: Java HotSpot(TM) Client VM, 1.6.0_10-ea-b07 OS: Windows XP, 5.1, x86 User Comments: try new Topcomponent in maven project
Created attachment 54362 [details] stacktrace
most probably fixed by http://fisheye.codehaus.org/changelog/mevenide/?cs=4809 http://fisheye.codehaus.org/changelog/mevenide/?cs=4810
Maybe I'm missing something but how can an NPE in apisupport be fixed by a change in MevenIDE? If a change in MevenIDE causes the bug to no longer be _triggered_, then fine, but an NPE is still a logic error.
well, the wizard was adding multiple dependencies. After each addition, the pom.xml file gets saved and project gets reloaded (I know it's not ideal, but that's how the SPI is designed right now) The dependency addition had a bug of not adding version to dependency in some cases. That rendered the pom.xml file invalid and the maven support fallbacked to "empty" definition of a project. The "nbm" packaging disappeared and the NbModuleProvider disappered from project's lookup -> causing NPE. The NPE itself shall not be fixed IMHO in the apisupport codebase. Erratic switches from "is netbeans module" to "isn't netbeans module" within a single New File wizard instance is not something we want to fix IMHO. Thanks for catching this and making me think harder about why the error disappeared. I'm pretty confident now the issue is gone. marking as fixed.