Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [p2-dev] Director problems

Hi Thomas, 

There are Manipulator objects who are responsible to persist gathered at runtime configuration data (in particular config.ini) 

Briefly, when you're trying to persist your runtime changes, the infrastructure checks whether simpleConfigurator bundle is listed and started in config.ini osgi bundles. 
If that condition is satisfied, installed IUs  will be persisted in, if not - in config.ini (as it is in your case).

In your config.ini simpleConfigurator is with start level 4 and is not marked to be started.
I have some troubles opening the repository but would you check in the content.xml whether the IU "toolingwin32.win32.x86org.eclipse.equinox.simpleconfigurator" is presented?
It is responsibe for setting start level 1 and mark the simple configurator bundle as started. 

But it is only applicable for win32x86 architecture - you have to define it in your profile (eclipse.p2.profile=Buckminster) as profile property.
I guess that is what lacks in your configuration.

I hope this helps.
If you have further questions, please let me know.

Kind regards,

-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Thomas Hallgren
Sent: Tuesday, July 20, 2010 1:32 PM
To: P2 developer discussions
Subject: [p2-dev] Director problems


I have serious problems creating products from scratch using the 
director. Everything works like a charm when I use the one from 3.5.2 
but if I switch to 3.6, the install it produces is broken. I've tried to 
install the IDE and it doesn't work.

I need help with this a.s.a.p. My knowledge about the code that produces 
the config.ini etc. is very limited and I would very much appreciate if 
someone who knows more in this area could have a look. The bug is:


Thomas Hallgren

p2-dev mailing list

Back to the top