I work on a application that recently switched to use rpms to install components in our application which uses the p2 director. We do this so we can easily apply patches for components without providing a completely new installation. Before, we used to have one feature that specified all of the plugins for the application and our .product file used that one feature. Our .product file was also responsible for specifying runtime levels and autostart flags for a few of our plugins. Since we moved to feature based components, our .product files feature has almost no plugins in it since everything has their own component now. So the autostart configuration for a plugin that isn't included in the .products feature isn't getting picked up. What appears to be happening is the director is managing the configuration/config.ini file and dynamically adding/removing plugins from it when features are installed and basically ignoring the products configuration specifications. Is there anyway to specify autostart or runtime levels for a plugin in a feature or a feature update site so that when the director installs the plugin, it knows to specify the correct runtime level/start flag?
Thanks
Max
Edit: Found this blog and used the "p2 Touchpoint Actions" instructions and got it to work. The only thing I had to change was:
instructions.configure =
setStartLevel(startLevel:4);
markStarted(started: true);
to
instructions.configure = \
setStartLevel(startLevel:4); \
markStarted(started: true);
[Updated on: Thu, 23 June 2011 16:35]
Report message to a moderator
] 
Search
Help
Register
Login
Home
