Community
Participate
Working Groups
Build Identifier: I20100429-1549 I'm trying to export a plugin from PDE into an existing OSGi app. When I do that, the plugin gets dumped in the plugins/ directory, but the path of the jar in the configuration/config.ini isn't updated. Reproducible: Always Steps to Reproduce: 1. Right click on a plugin, run 'Export' 2. Select 'Deployable Plugins and Fragments' 3. On the 'Destination' tab, select 'Directory' and point to the dir above the target plugins/ directory. 4. Export. After the export is completed, the app uses the old jar. If I manually modify configuration/config.ini to point to the newly created jar, the app uses the new jar.
Oops - I didn't mean to assign that to 4.0.
This only seems to happen when the target OSGi app was generated from a product file with the "Generate metadata repository" checkbox set (the default). If I generate the product with the checkbox unset, then I get a very short config.ini that doesn't specify the name of my plugin. The app picks up my plugin when it runs.
We don't have a "export plugin into an install", only into the running host or a folder. If this is working without the metadata checkbox, you probably have a product that uses org.eclipse.update.configurator. This scans the plugins folder and uses everything that is found there. There is no explicit "install" steps required. Checking the metadata box results in p2 installed product which does require explicit install steps. Although, if the product used p2 dropins, then the bundle would get picked up that way. I'm going to move this to UI, perhaps we can expand on the install into host to include installing into other products.
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. -- The automated Eclipse Genie.
