Bugzilla – Full Text Bug Listing
| Summary: | Enhanced OSGi Launcher Definition Editor | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Naci Dai <naci.dai> |
| Component: | Libra | Assignee: | Project Inbox <libra.launchers-inbox> |
| Status: | NEW --- | QA Contact: | Naci Dai <naci.dai> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | kaloyan, murat.yener |
| Version: | unspecified | Keywords: | plan |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Moved to M7 Juno M7 passed away some time ago. Can we have this enhancement targeted appropriately? Perhaps to 0.3 or Future? Moving to Future. Please, target to something more appropriate. |
We need a better target definition editor and a bundle selector (the list of bundles that will be installed and started) for the OSGi Launchers. The goal initial goal is to enhance the OSGi Framework Instance Editor: 1) Save the target definition under the servers folder. 2) Integrate with the default target definition editor. 3) Add a bundle selector (similar to PDE OSGi Launchers bundles tabs). and integrate with Virgo bundle overview a) Validate b) Add required c) Show selected etc. 4) Add an extensible "Service" configuration tab to add, set and change common osgi service VM parameters (http port, jmx port, etc.)