Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358437 - [Subsystems] Support OSGi subsystems
Summary: [Subsystems] Support OSGi subsystems
Status: NEW
Alias: None
Product: Virgo
Classification: RT
Component: runtime (show other bugs)
Version: 3.0.0.RELEASE   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 358440 358449 358451 358452 358454 358536 358537 358539 358540 358541 358543 358544 358546 358547 358548 358549 358550 358551 371427 358441
Blocks:
  Show dependency tree
 
Reported: 2011-09-21 10:59 EDT by Glyn Normington CLA
Modified: 2012-10-02 03:42 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Glyn Normington CLA 2011-09-21 10:59:26 EDT

    
Comment 1 Glyn Normington CLA 2011-09-21 11:06:12 EDT
Logging the dependency on Libra tooling for subsystems. Without that, users will have to construct subsystems manually.
Comment 2 Glyn Normington CLA 2011-09-21 11:09:14 EDT
The requirement is for Virgo to support subsystems as defined by OSGi RFC 152, a public draft of which should appear before long. A subsystem is a standardised form of multi-bundle application, analogous to Virgo's PARs and plans.

The intention is to implement base, non-subsystem specific changes in Virgo which will be required to support subsystems, then prototype the draft specification, and later finalise the implementation when the spec freezes.
Comment 3 Glyn Normington CLA 2011-09-23 05:46:45 EDT
Targeting 4.0.
Comment 4 Glyn Normington CLA 2012-10-02 03:42:41 EDT
The only feature of subsystems which seemed to be specifically required by Virgo users was implemented under bug 358441 in Virgo 3.5.0. The cost/benefit ratio of the remaining features is very high and so subsystems is unlikely to be implemented in Virgo unless demand increases substantially and/or committers or contributors step forward to implement significant chunks.