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.
Currently apisupport.installer/src/org/netbeans/modules/apisupport/installer/actions/BuildInstallersAction.java does a lot of specialized stuff before passing control to the NBI scripts. This makes it difficult to build installers from the command line (incl. from CI). apisupport.installer/release/installer.xml could be created that would encapsulate most of the functionality of the current BuildInstallersAction, which would then be simplified to just call a target in suite.xml delegating to installer.xml. (This would be better also since findGenXml is wrong - it looks up NBINSTALL/harness/nbi/stub/template.xml even if the suite is configured to use a different platform!) As to how to fix up apisupport.installer.maven, well, that is just a mess. Would need to produce an actual Maven plugin that could be included as a goal in your POM, somehow reusing the current NBI scripts. Ideally the NBI infrastructure would be rewritten to be a Java library with a thin Ant task wrapper and a thin Maven mojo wrapper.
I am not in need of touching code I've never seen that sort of works. Jirko, as installer master, do you want to do something with this or do we close as won'tfix?
(In reply to comment #0) > Would need to produce an actual Maven plugin that could be included as a goal > in your POM, somehow reusing the current NBI scripts. Note that this is long since done. > Ideally the NBI > infrastructure would be rewritten to be a Java library with a thin Ant task > wrapper and a thin Maven mojo wrapper. (but this is certainly not)