BundleActivator start being called out of order relative to service activate

[scottslewis]

When bundle is installed and then started, with a service instantiated and validated, the order of method invocations seems to be:

Activator.__init__
@Validate
Activator.start

This is unexpected ordering, as in OSGi the Bundle start method is guaranteed to occur prior to any service registration and subsequent validation.

Thomas indicates this appears to be a bug associated with this line of code:
https://github.com/tcalmant/ipopo/blob/master/pelix/ipopo/core.py#L605