Geek Answers Handbook

Using PDE, p2, and AdvancedInstaller together

I am creating an Eclipse RCP application with a PDE version on the command line in Eclipse 3.5.1. Then I use AdvancedInstaller to create an installer for the RCP product. I think the context will be similar to InstallShield and similar packages instead of AdvancedInstaller.

If I include p2 initialization in my build, can I continue to distribute the product as a standalone installer (still released by the Advanced Installer) and do updates through the update repository created by p2?

+4
source share
2 answers

I don’t know anything about AdvancedInstaller, but I assume that this is essentially a package of the RCP product that comes from your assembly.

Yes, you must be able to do what you describe. The inclusion of p2 in the assembly should not change anything with respect to this installer; the assembly results will still be a running RCP product, which you can package.

The only difference is that the product you are packaging will be properly configured for p2. (This will actually be the result of the install operation p2). In addition, the assembly will be able to create a p2 repository for the product, which you can post on the Internet to upgrade the version to version.

+1
source

Something else to consider is that you can let P2 handle part of the installation itself, rather than writing it to the installer. For instance. if you need to install different product options (different sets of plugins), you can use P2 Director to provide the product as part of the installation.

P2 is a pretty cool software product that is worth the time.

+1
source

More articles:


All Articles