Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
None
-
None
Description
SPI-Fly is subject to start ordering constraints. This is because weaving hooks are not retroactive in the framework, they only take effect at the moment they are registered. As such they do not operate on previous possible candiates.
It would be nice if SPI-Fly could trigger a refresh on already installed bundles such that weaving would take affect on them. This would eliminate the start ordering problem. Making this a configurable feature would also probably be a good idea.
Attachments
Issue Links
- Blocked
-
ARIES-1814 Solve the start order limitations with SPI Fly
- Resolved