Community
Participate
Working Groups
Build ID: 3.4 Preferences -> PDE -> Target Platform If you're using a shared installation the bundles from your dropins are missing ! You only see all bundles from pool (and there you are seeing too much see Bugzilla 238949) and you dont see the bundles from your dropins. workaround: The only way to change this is using Add.. for all plugins folders inside your dropins. If you have structured your dropins, this means you have to select each plugins folder from there. It can happen easily to forget something or loosing the overview. btw: using stand-alone installations all dropins were recognized as expected
Do bundles exist in the bundles.info (p2 metadata)?
Ekkehard, are you aware of how the new target platform preference works? http://mea-bloga.blogspot.com/2008/04/new-target-platform-preference.html
hi chris, yes, I'm aware of how the target platforms work now. all works well if I'm using 'normal' installations. But if I'm using P2Installer, install SDK as shared using a bundle pool then the target platform gives me no way to get the bundles from the dropins folder. some screenshots follow to demonstrate and yes: the bundles.info shows the bundles from dropins
Created attachment 106368 [details] installed software includes dropins here you see the installed software the openArchitectureWare plugins are from dropins folder and correctly recognized
Created attachment 106369 [details] target platform has no knowledge of bundles from plugins here you see the target platform there are only the bundles available from the bundle pool (as described in bug 238949 here are ALL bundles from bundle pool, not only the bundles installed in current running application) checkbox selected or not doesnt matter of course tried all combinations of apply, reload etc
Created attachment 106370 [details] all works well if not P2 - shared installation here you see the same scenario but using a normal install, not via P2 Installer - shared then all dropins are known and also the bundles from the current running eclipse the problem isn only using shared installations
We would like to re-work the way target platforms are discovered in 3.5. (I'm not sure we have a bug/feature open for this yet, but it is mentioned on the PDE planning wiki: http://wiki.eclipse.org/PDE/Ideas#Target_Management) Essentially, we want to use a new API provided by p2 or the runtime that lets use reflection on an installation to see what bundles are installed. This should help reduce these sorts of problems.
Darin, I read about the ideas for target platform management - the greatest thing for me would be to have more then one target platform in a workspace. then I could simplify my installations of workspaces, which esp. important for use of Mylyn tasks, whats difficult with more then one workspace. does it mean that at the moment the behaviour with shared installations (only knowing all bundles from all shared applications, but not knowing the bundles from dropins and current installation) is a "feature" of 3.4 and not a bug ? then I would revert to single installations until 3.5 because the comfort on the one side with using a bundle pool is less worth then the comfort of automagically scanning dropins and haveing my own application as host. ekke
In your example, is the "e34pool" directory an "root install directory" that contains a "configuration" directory? If so, then this is a bug. However, if this is the bundle pool location, to which two (or more) configurations point, then this is not a bug. You should be able to point to an install location, and the "configruation" area will tell PDE which bundles from the pool are installed in each installation.
Created attachment 106432 [details] directory structure e34pool as you can see, e34pool is a root directory I created only this directory, then P2 Installer fills this bundle pool location with content
Created attachment 106433 [details] p2installer.ini p2installer.ini was modified and points to a local file: .../e34p2installer/sdk-installer.properties
Created attachment 106434 [details] bundleLocation .../e34p2installer/sdk-installer.properties only thing modified was: eclipse.p2.bundleLocation pointing to the root of e34pool
In the "configuration" directory is there an "org.eclipse.equinox.simpleconfigurator" directory containing a "bundles.info" file? and does that file contain entries from the "Dropins" folder?
Created attachment 106444 [details] bundle.info the "configuration" directory of e34pool is empty but the "configuration" diretory of e34modeling has an "org.eclipse.equinox.simpleconfigurator" directory containing a "bundles.info" file. see attached and this file contain entries from the "Dropins" folder for me this is OK, because this dropins folder is local to e34modeling Eclipse Application. another Eclipse Application (e34osgi_rcp) has also an "own" dropins folder both applications use their local dropins folder together with the bundle pool why should the bundle pool have knowledge of the dropins folders located at applications which share the bundle pool, but not their dropins its also possible to have an extra dropins folder (as I desribed in my blog http://ekkes-corner.blogspot.com/2008/06/eclipse-ganymede-p2-shared.html) using -Dorg.eclipse.equinox.p2.reconciler.dropins.directory in the eclipse.ino of the Eclipse Application
OK, so I think this is a dup of bug 235336 - PDE is not getting the correct configuration location in this case and we are scanning all bunldes in the location rather than using the correct bundles.info. *** This bug has been marked as a duplicate of bug 235336 ***
thanks, darin, so I'll watch bug 235336 and test again after fixing it. ekke
just tested with 3.5M1 and can confirm: Bugfix 235336 also fixed this bug thanks ekke
