Community
Participate
Working Groups
I20050209 Currently in the Product Configuration Editor, on the first page you can only specify one format to export things in: zip. Other options are needed. For example the Deployable plug-ins and fragments export wizard provides an option to deploy into a directory structure. The product exporter should allow this too in order to make it more convenient for its output to be fed into other programs (such as install builders). Also, for tighter integration with installers, hooks should be provided to allow plug-in writers to create their own product export options. For example it should be possible for me to write a plug-in that would use Nullsoft or Installshield or some other installer to create a packaged EXE format.
I split off the part about hooks for extending the product export options into its own entry, bug 85443. So this entry is only to request some other options, in particular one to deploy into a directory instead of a zip file.
It seems there is some separation between the form of the plugins in the output and the form of the output. We should make more generic the desire to have things in jars (currently you have ot say you want an update thing just to get Jar'd plugins). In this case, since the export operation does not actually update the site.xml or anything, we can simply remove the references to Update in the export wizard. As was pointed out above, having the final output in a dir or a zip is reasonable as well. This way users wanting to do an update site simply say, jar the plugins and put the output in a dir.
done a while back.
