Bundle update compatibility checking via enhanced component lifecycle
- CSet as Current
- Mark as completed
- Delete
responsible
not set Set user
responsible
not set Set
start date
not set Set
budget
- About 14 years overdue
- Last activity in over 13 years ago
Description
Hookable lifecycle, lifecycle events. Type compatibility verification on "resolve", "update", service binding events. (We may want to split into two separate milestones.)
Acceptance criteria: A demonstration set of bundles is available which
- has a bundle that acts as filter on bundle install and bundle update
- listens to bundle lifecycle events and outputs real-time "log" of lifecycle events in the framework
When updating a .groovy-only bundle, the type-based comparator kicks in to verify that the new version is compatible with the current one. If yes, update is run, if not, the current bundle is left in the state in which it was when update was called. Includes JavaDoc and PDF documentation.
Acceptance criteria:
- Set of testing bundles in which there are compatible and incompatible differences in version streams.
- Framework spits error messages when user tries to update a bundle to incompatible version.
Tickets
Reports & Metrics
Hours
Home / Developer API / Tour / Get a Project - Solutions for Bug & Issue Tracking, Collaboration Tools, Subversion Hosting, Git Hosting
Cosi - the obsessively black-box component model in osgi style is powered by Assembla.