Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358551 - [Subsystems] Virgo-specific Eclipse IDE support for subsystems
Summary: [Subsystems] Virgo-specific Eclipse IDE support for subsystems
Status: NEW
Alias: None
Product: Virgo
Classification: RT
Component: tooling (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 358440
Blocks: 358437
  Show dependency tree
 
Reported: 2011-09-22 05:32 EDT by Glyn Normington CLA
Modified: 2012-06-22 06:36 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Glyn Normington CLA 2011-09-22 05:32:31 EDT 
This bug covers any Virgo-specific tooling support needed over and above that provided by Libra.
Comment 1 Glyn Normington CLA 2011-09-23 05:46:42 EDT 
Targeting 4.0.
Comment 2 Miles Parker CLA 2012-04-20 17:39:07 EDT 
What's involved in this? There is some support already in RepositoryContentProvider, but I'm not sure that's relevant to this usage? Is this expected to be supported on the runtime side soon?
Comment 3 Glyn Normington CLA 2012-04-23 04:46:24 EDT 
The work in this bug will hopefully be small or zero since Libra's remit is to support OSGi standard features , of which subsystems will soon be one.

In general terms, this and bug 358440 will enable the Virgo IDE tooling to develop OSGi standard subsystem archives and deploy them to Virgo. The most likely Virgo-specific aspect is to drive the Virgo deployer mbean when deploying subsystems.

This won't happen any time soon as there is a ton* of work to do on the runtime side to support subsystems.

(Note that weighing code size is just about as scientific as estimating KLOCs.)