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.
I had: <makenbm file="tasklist-usertasks.nbm" module="${nb.modules.dir}/tasklist-usertasks.jar" productdir="${netbeans.dest.dir}/${cluster.dir}" homepage="http://tasklist.${homepage.base}/updates/tasklist-usertasks.html" distribution="http://${dist.base}/tasklist-usertasks.nbm" needsrestart="false"> <license file="${license.file}"/> <signature keystore="${keystore}" storepass="${storepass}" alias="${nbm_alias}"/> </makenbm> and it finished OK but did NOT included module jar into target nbm. There is hidden contract between <genlist> and <makenbm>. My expectation is: - pass a <fileset> defined by <pattrenset> to <makenbm> explicitly as in <genlist> case - use module parameter as additional input or deprecate it - print out message that tasklist/usertasks.files are processed
module parametr is used to resolve the module codenamebase so it is not ignored, the the filelist of file, which should included in NBM is being read from, update_tracking/{module-dashed-codenamebase}.xml file, which is being generate on behalf of <genlist> task. If you'll projectize your build then you can't see any errors regarding NBMs.
At least copy the description to a documentation. <makenbm> task semantics have changed in such way that it can silenty break build if not revisited.
The task should presumably issue a warning at least if its fileset does not include a module JAR.
Making as WONTFIX