-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Description
I would ideally post this in GitHub discussion, but this project doesn't have that turned on, so asking here.
I noticed when installing a feature in my project, that some of the bundles in the feature were not being started. I was able to fix it by changing the order of the bundles listed in the feature. Which seemed odd to me. So after doing some debugging, the reason seems to be that after the feature runtime install phase some of the bundles go to the RESOLVED state.
So my question is: Is there a reason for the check in startBundles to limit to INSTALLED only? Because from my perspective if we expanded it to include RESOLVED as well, that would fix some bundles not being started that I would expect to be started.
Thanks
Metadata
Metadata
Assignees
Labels
No labels