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 20071102050220) VM: Java HotSpot(TM) Client VM, 1.5.0_09-b03 OS: Linux, 2.6.17-5mdv, i386 User Comments: new action wizard in maven nbm module
Created attachment 52445 [details] stacktrace
NbModuleProvider.getManifestFile() is returning null, I think, which would probably be an issue with the Maven NBM project type? Can make apisupport code more robust - will skip the step of adding the OpenIDE-Module-Layer line to manifest if there is no known manifest. Checking in LayerUtils.java; /shared/data/ccvs/repository/apisupport/project/src/org/netbeans/modules/apisupport/project/layers/LayerUtils.java,v <-- LayerUtils.java new revision: 1.42; previous revision: 1.41 done
yup. The manifest getter returned null because it didn't exist yet. I just took a simple jar project and converted it to nbm project, forgotten about adding the manifest file. Should not be common once we get a proper archetype for nbm projects. A proper fix would be probably to convert the manifest getter in the SPI to return File rather than FileObject and create it on the fly when the file doesn't exist and the is necessary.
there are now nbm archetypes released. Works fine in te 3.1-SNAPSHOT of mevenide. The apisupport-maven bridge modules puts it in a privideged position in the archetypes list. Decreasing priority, unlikely to happen.
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. We apologize for any inconvenience. Thank you. The NetBeans Team