For now, the config.ini is probably your best option. In Eclipse 3.5 Galileo, you will be able to use P2 touchpoint advice file (p2.inf) to indicated your bundle should be "markStarted" as well as set its "startLevel".
See http://wiki.eclipse.org/Equinox/p2/Engine/Touchpoint_Instructions The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of J B Sent: Wednesday, April 15, 2009 3:52 PM To: equinox-dev@eclipse.org Subject: [equinox-dev] Autostarting Bundles I have a small server-side equinox application running. I would like to autostart a couple of other bundles automatically. The Eclipse-AutoStart is deprecated, and the Bundle-ActivationPolicy only accepts 'lazy' as a value. Is there an accepted way to auto start bundles without having the explicitly in the config.ini? We have used a solution in the past that require the plugins wishing autostart to register an extension to a service that will start them on their behalf. But it seems like there must be a different way. Any thoughts? Birch _______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
