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 7.0 M2 (Build 201010151251) Java: 1.6.0_20; Java HotSpot(TM) 64-Bit Server VM 16.3-b01-279 System: Mac OS X version 10.6.4 running on x86_64; MacRoman; en_US (nb) Userdir: /Users/tomas/.netbeans/7.0m2 --------- - create netbeans module under maven category - clean and build - run cd /tmp/nbmm2; JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home "/Applications/NetBeans/NetBeans 7.0 M2.app/Contents/Resources/NetBeans/java/maven/bin/mvn" -Dnetbeans.execution=true nbm:cluster nbm:run-ide Scanning for projects... ------------------------------------------------------------------------ Building nbmm2 NetBeans Module 1.0-SNAPSHOT ------------------------------------------------------------------------ [nbm:cluster] Created NetBeans module cluster(s) at /private/tmp/nbmm2/target/netbeans_clusters [nbm:run-ide] ------------------------------------------------------------------------ BUILD FAILURE ------------------------------------------------------------------------ Total time: 1.179s Finished at: Mon Oct 18 11:21:30 CEST 2010 Final Memory: 5M/81M ------------------------------------------------------------------------ Failed to execute goal org.codehaus.mojo:nbm-maven-plugin:3.3:run-ide (default-cli) on project nbmm2: The parameters 'netbeansInstallation' for goal org.codehaus.mojo:nbm-maven-plugin:3.3:run-ide are missing or invalid -> [Help 1] To see the full stack trace of the errors, re-run Maven with the -e switch. Re-run Maven using the -X switch to enable full debug logging. For more information about the errors and possible solutions, please read the following articles: [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginParameterException
The NB installation location must be set in settings.xml. Did not realize this archetype needed that parameter. Running the Module Suite wizard does this, so that is probably the best workaround for now. Anyway it is best not to use (standalone) Module or Module Suite archetypes for Maven; better to create a Platform Application and add modules to it. The resulting project will be portable, since the NB platform is taken from the Maven repository, not your local installation.
Was already fixed in e5bdd4c9a2af.