1) Can we create an installer (for RCP products) that allows users to choose which components they want to install?
2) Is it possible to change the default structure that an installer creates? (not having the Commons directory for instance).
3) Is the server purpose just authentication or some part of the installer is not built locally?
Daniel, regarding your questions about OneInstall.
1) Can we create an installer (for RCP products) that allows users to choose which components they want to install?
- Yes with one install you will be able to deliver RCP products, and customize how the installer behaves. OneInstall also create your own "Module" to allow a user to choose components.
2) Is it possible to change the default structure that an installer creates? (not having the Commons directory for instance).
- Yes OneInstall allow you to customize the default Sequence of OneInstall allowing you to add/remove functionality to your installer.
3) Is the server purpose just authentication or some part of the installer is not built locally?
- Right the Pulse Server is only used at installer build time for authentication purposes, all the build process goes on your side. Your installer will have no knowledge of the Pulse Server, in other words, your running installer does not need to talk to the Pulse-Server, if you are building a RCP Installer.
The installer generated by OneInstall creates something like this:
<Product dir>
<Commons>
<plugins>
<features>
Product.exe
How can I customize it using a Sequence in order to keep the original directory structure that Eclipse has?
Do I have to do something in Java or is this just a matter of declaring configurations in a XML file?
I already read the documentation, but I have no clue of what to do.
Daniel, while I was reviewing your case, I found that you may not want to remove the Commons directory from the Oneinstall RCP install, it contains many extra data used by both OneInstall, and the Eclipse Equinox framework on this directory. However you could do this with a major customization of OneInstall. I've worked on an example for you on how to do this.
The attached file contains some Eclipse projects, and the installer.xml
- installer.xml changes (Search on the file for the words "ONEINSTALL EXAMPLE"):
- The first change is to add the <extension> to the installer target, this will tell the oneInstall tool that there is an extra plugin on the given update site.
- The second change is where we override the default sequence to pick our customization.
Eclipse projects contains the a site project which you must build with the aid of the PDE, this is the one you will use for the <extension>. Other projects are the example rcp application and the Custom processor.
Follow the OneInstall tool to get a new RCP installer project to try this, the OneInstall Tool is on the one install tool installer run it again to configure a new project. In my case I ran this example with
I should also mention that with our new Product "Secure Delivery Center (SDC)" you could also do this and much more, by default Installers builded by SDC does not drop a Common directory. SDC Installers are also based on OneInstall technology. To get more information about SDC please visit:
Installer customizations and pulse server
Posting Permissions
Reply With Quote