I work around the limit by including large zip files in the distribution relative to the installer location. The folder the installer is located in can be referenced with the $EXTRACTOR_DIR$ variable.
We work around the problem by splitting the installer up into multiple merge modules. Two developers can work on two merge modules that each go into the same installer. If your project is big enough to support multiple developers, it is probably al...
You might be able to do this with the ExecuteCustomCode. Java can put the stdout/stderr in a console window and run the command using the Runtime.exec() command.
If you use an external zip utility, you can run the Execute Command action to unzip it. Just make sure to not check the box "Suspend installation until process completes." If you need a listener for it, you can scan the processes on the system and ...