Community
Participate
Working Groups
Build Identifier: 20100218-1602 As Andrew Niefer points out in his two blog entries http://aniefer.blogspot.com/2009/07/composing-and-updating-custom-eclipse.html and http://aniefer.blogspot.com/2009/07/adt-part-2-more-like-epp.html it is now (3.5/3.6) impossible to create an RCP app that has custom updatable features without resorting to full Ant driven build and delving deep into p2 configuration. This is too steep a barrier for most RCP programmers. I propose that a 4th option be placed in the Export/Deployable Features dialog below export into host that is called "Export and install into built RCP application" where the option would automate the steps of building an update site, follwoed by p2 director calls of installing into each platform version. Reproducible: Always Steps to Reproduce: Try making a custom updatable RCP app as outlined in blog mentioned above.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
One can still install features using Import / Install / Existing Installation. There is no symmetry on the Export side which is not helpful to beginning RCP programmers. My proposal is to add a fourth option under Export / Deployable Feature (AND Deployable plug-in) / Destination tab named Existing Installation. I just discovered that you can CHOOSE the destination under the 3rd option "Install into host. Repository:" but it is totally unclear on how to proceed to install into an existing installation: My proposal would be to change the wording into "Install into Existing installation" to make wording similar as Import option and to add a tooltip to help locating the proper repo location. Any way I cannot get this option to work when the host is not the current development environment
Product file allows root setting now
