[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Spoofing a profile
- From: Pascal Rapicault <pascal.rapicault@xxxxxxxxxxxx>
- Date: Fri, 22 Nov 2013 16:12:38 +0000
- Accept-language: en-CA, en-US
- Delivered-to: firstname.lastname@example.org
- Thread-index: AQHO5uVi1Di37EC7ukiz6CRhj8HNcZoxZ8Vw
- Thread-topic: [p2-dev] Spoofing a profile
I think there are two ways to do this:
1) Have a profile generation bundle starts eagerly (before any p2 related activity starts) and create the profile such that when the profile registry looks for the profile, it is already created
2) Have the simpleprofileregistry look for an extension (or service) that invokes the profile generation bundle code (probably in a separate bundle) when the profile can not be found.
I prefer #2 because it is more integrated and does not incur a cost when the p2 is not used.
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Krzysztof Daniel
Sent: November-21-13 1:13 PM
Subject: [p2-dev] Spoofing a profile
after extending simpleconfigurator to read many .info files, I started looking at SimpleProfileRegistry and attempted to spoof a profile from a running platform following afterthefact project from the p2 incubator and earlier work done in bug 215559. Current state of work is in https://git.eclipse.org/r/18686, but I run into a problem - SimpleProfileRegistry looks like a wrong place for spoofing a profile, because any attempt to use *Plan* classes from the director plugin results in circular dependencies.
What would be the suggested way to implement this?
Krzysztof Daniel <kdaniel@xxxxxxxxxx>
p2-dev mailing list