Eclipse 4 RCP. The structure of an Eclipse application is described via an application model. At startup, this application model is constructed based on multiple configuration files and adjusted by code logic resulting in a runtime application model. This runtime application model is the basis for the running application and it is kept in sync with the application during runtime by the framework. This model contains the parts of the application as individual model elements and their hierarchical relationship. Some of these model elements are visible to the user. For example, windows, parts (views and editors), menus, toolbars. Other elements are not directly visible to the user, for example, handlers, commands, and key bindings.
Each model element has attributes that describe its current state, e.g., the size and the position of a window. The base of the application model is typically defined as a static file. 6.1. The following table describes the supported URI patterns. 6.2. 6.2.1. 6.2.2. 6.2.3. Configuring your build environment with maven.
Equinox/p2/Adding Self Update to an RCP Application-3.5. This page consolidates information about how to add p2 self-updating support to your RCP application using the p2 provisional APIs in 3.5. We start with the RCP Mail example application and modify it in different ways. Adding p2, building, and provisioning your application with p2 The process for setting up your application to update with p2 involves several steps. The p2 bundles must be added to your application. This can be expressed by including the p2 bundles in one of your product's features (using the feature org.eclipse.equinox.p2.user.ui as a guide). It can also be done by expressing requirements in your features and letting the p2 install of your application pull in the right code.
Set up a build for your product. This process is described in more detail in Andrew Niefer's blog post on the topic. An example build based on a modified RCP Mail application can be found here. Configuring the user's default repositories Configuring the p2 UI Reusing the Eclipse SDK UI in its entirety. Kai's Blog » RCP Self Provisioning with P2: It Works!!! I finally could create the mail demo RCP app using p2 to update itself! My environment is Windows Vista, Java 6, Eclipse 3.4 RC4.
Here are the steps that describe how I p2-enabled the mail demo: 1. Created the mail demo (project p2-maildemo) 2. Created a product configuration p2-maildemo.product 3. To get the final update work in the installed product, it is also necessary to include the following 3 plug-ins with dependencies in the product configuration: - org.eclipse.ecf.provider.filetransfer - org.eclipse.equinox.p2.touchpoint.eclipse - org.eclipse.equinox.p2.touchpoint.natives 4. 5. VM arguments: -Declipse.p2.data.area=c:/java/RCP/p2-maildemo/install/p2 6. 7. So far so good! Now I wanted to create a new version 1.0.1 of the product and update the installed version 1.0.0: 8. 9. 10.
The first thing I noticed was that my installed 1.0.0 did not find any update. 11. 12. 13. I am so happy that I finally got this to run Many thanks to everybody who helped me. Kai. P2 in RCP Application. Building p2 RCP products in Eclipse 3.5M6. We can also call this "Building for the Cloud" just to take advantage of the newest buzz word. Susan Franklin McCourt put together a nice wiki page covering how to add p2 self-updating support to your RCP application.
One of those examples was called "Updating from the Cloud". As part of preparing for EclipseCon, I put together a simple releng product build that builds this cloud product for p2. The cloud bundle "org.eclipse.equinox.p2.examples.rcp.cloud" is available in CVS together with a releng project that I created. [Edit 2013/07/03: Eclipse CVS has migrated to git starting in 2010.
The examples are now available under the examples folder in To run this example, check both projects out into your workspace, and read the rcp.cloud.releng/readme.txt. Builder Setup p2.gathering In 3.4, p2 metadata was generated by running the metadata generator on the binary jars that were the result of the build. Generate metadata from source. Incompatibilities between Eclipse 3.5 and 3.6.