-
-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
Description
I think this is the load order I want to follow, but we should figure this out so that it works well.
- OSGi detects a new/updated module
- Load the module's information
- Download any required modules (if available)
- Download any dependencies
- If this fails, stop loading.
- Notify the module that it's been started and register any modules, managers, etc.
Some things to consider:
- How we want module overwriting to work, since that's a feature that I'd like to have if possible.
- Detecting cycles in dependency graphs and refusing to load them.
- Creating a dependency graph and not loading modules if their dependents aren't available (basically, fail gracefully by removing features until we get into a workable state, then let the user know)
Reactions are currently unavailable