| Summary: | Integrate p2 explorer from Oomph to PDE | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Mikaël Barbero <mikael.barbero> |
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | daniel_megert, Ed.Merks, Lars.Vogel, stepper, Vikas.Chandra |
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Mikaël Barbero
+1 if that comes without additional dependencies. Alternative solution might be p2-browser (https://github.com/ifedorenko/p2-browser) Mikaël, is it OK to assign the bug to you? (In reply to Lars Vogel from comment #1) > Mikaël, is it OK to assign the bug to you? Not currently, sorry. p2 is often used without PDE being installed. I don't see why any PDE-unspecific kind of p2 add-on should exist in PDE, but that's not my construction place. We certainly won't move Oomph's Repository Explorer to PDE, so I suggest to close this bug as wontfix. (In reply to Eike Stepper from comment #3) > p2 is often used without PDE being installed. Would you be interested in contributing it to p2? It depends on oomph.base, oomph.base.edit, oomph.p2, oomph.p2.core, oomph.p2.edit, oomph.ui, and oomph.util. It makes no sense to move oomph.base, oomph.base.edit, oomph.ui, and oomph.util outside of the Oomph project. What is to be gained by moving it? (In reply to Eike Stepper from comment #3) > p2 is often used without PDE being installed. I don't see why any > PDE-unspecific kind of p2 add-on should exist in PDE, but that's not my > construction place. We certainly won't move Oomph's Repository Explorer to > PDE, so I suggest to close this bug as wontfix. +1. |