Karl Weber Messages: 63 Registered: September 2010
With a target for an RCP e4 application based on 4.2M5 the configuration admin service does not start automatically. To be explicit: When the org.eclipse.equinox.cm-1.0.300.v20111215-1210 plug-in is added with default startlevel and default auto-start the service does not start. Hence, my components referring to it remain unsatisfied. The service does start and things work as expected, when I set the startlevel to 2 and auto-start to true for the cm plug-in.
With corresponding targets based on 4.1 (and 4.1.1) and org.eclipse.equinox.cm-1.0.300.v20101204 this has not been necessary, i.e. things work with default startlevel and default auto-start.
Has something about the configuration admin changed?