|Re: [equinox-dev] Question on Profiles / p2 and standalone Osgi|
The profile is not here to instruct p2 what should be installed in your system. Instead you need to think of it as the record of what has been installed.
I think that the issue you are encountering is a tooling one where when you are starting an application from within Eclipse, no corresponding profile is created and as such any subsequent p2 operation can be problematic (https://bugs.eclipse.org/bugs/show_bug.cgi?id=250126).
There is currently two work around:
1) You create a profile for your installation using the admin ui. When you start your application from within the IDE you set the vm arg eclipse.p2.data.area to point at the p2 folder that contains the profile you are running (e.g. -Declipse.p2.data.area=/Users/Pascal/Downloads/eclipse/p2/). You may also want to specify the ID of your profile by setting eclipse.p2.profile as a vm arg (e.g. eclipse.p2.profile=""> 2) You write a bundle that looks around in the running system, generates metadata representing it, and fake up an installation into a profile (you can find most of the code for generation in the publisher bundle). This bundle would be running in the application started. This is really a HACK and should not be used in real systems. I'm giving you this approach as a way for you to progress, but using this in a real product would result in not guaranteeing unicity of metadata, would not allow you to manage all the external files, and finally would have a cost on startup to update the system.
Chase Wolfinger ---05/14/2009 09:52:01 PM---Hello - I am trying to use profiles with a standalone osgi
Chase Wolfinger <chase.wolfinger@xxxxxxxxx>
05/14/2009 09:52 PM
[equinox-dev] Question on Profiles / p2 and standalone Osgi