Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 358551

Summary:	[Subsystems] Virgo-specific Eclipse IDE support for subsystems
Product:	[RT] Virgo	Reporter:	Glyn Normington <glyn.normington>
Component:	tooling	Assignee:	Project Inbox <virgo-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	eclipse, mlippert
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:	358440
Bug Blocks:	358437

Description Glyn Normington

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

2011-09-23 05:46:42 EDT

Targeting 4.0.

Comment 2 Miles Parker

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

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.)