In the config.ini we set the default p2
profile name and the p2 data area. Where are the known and cached
repos stored? We aren't explicitly clearing (or saving) any information
in the p2 data area except for the profile.
If there are things missing (or cleared)
from the profile that would be useful, file a bug (even better if you can
explain where the data is stored or how to add the info to the profile).
The code used to create the profile IUs is basically what was available
in the p2 afterthefact bundle.
Ian Bull <irbull@xxxxxxxxxxxxxxxxx>
P2 developer discussions <p2-dev@xxxxxxxxxxx>
2009/10/28 09:47 PM
Re: [p2-dev] Self hosting with a p2
Thanks Darin, I was playing with this feature and it's
Sorry for all the questions, but what about other things in the p2 data
directory (and p2 properties) such as known (and cached) repos? Are
these cleared each time? (it looks like it, but I just wanted to
make sure this was by design).
On Wed, Oct 28, 2009 at 6:14 PM, Darin Wright <Darin_Wright@xxxxxxxxxx>
The profile is regenerated on each explicit launch (run
or debug), but it
is re-used on "restart" operations initiated from the target
- so you can
install software & restart the same profile.
During subsequent launches, will "installed" bundles still be
or is the profile regenerated from the launch configuration each time?
On Thu, Oct 22, 2009 at 2:28 PM, Curtis Windatt <Curtis_Windatt@xxxxxxxxxx
The PDE team is looking to add a new enhancement for M3 that will
hopefully help out p2 developers. When self-hosting, the launched
workbench currently must reuse the profile from the host. This can
it difficult to test p2 code that modifies the profile. This enhancement
would generate a profile containing metadata for the launched plug-ins
set the profile as the default for the target workbench. https://bugs.eclipse.org/bugs/show_bug.cgi?id=250126
There is a patch on the bug that adds a new check box to the configuration
tab of the PDE launch configuration. By checking the generate p2
option, everything should happen during the launch.
I'm hoping to get some feedback from p2 users/developers. If you
give the patch a try, or try out the feature in M3 and post feedback on
the bug or this mailing list that would be great.
I haven't been able to get it to work for 3.4 targets, can anyone on the
list point out if there were any changes between 3.4/3.5 in where/how the
profile is stored by the simple profile registry?