Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PDE/Incubator/XtremeSelfHosting"
(New page: Note This is W o R k I n P r O g R e S s S It all started with "install bundles in running Eclipse", but from others comments (e.g. in bug198189), seems problem is more general. Aim...) |
(→Project overview) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | === Work Area === | |
| − | + | Better integrate cooperation between Eclipse host and running instance in self-hosting. | |
| − | + | ==== Project overview ==== | |
| − | + | ||
| + | see also bug198189 | ||
| + | |||
| + | Developer will have a better control over and insight into his running Eclipse/Equinox/OSGi | ||
instance | instance | ||
| − | + | ||
| − | * | + | Features: |
| − | * | + | * Remotely observe and manage instance bundles |
| − | * | + | * Install bundles in target instance from host workspace |
| + | * Follow instance logs in host environment | ||
* inspect services (the same as in bug Bug 217738, but remote) | * inspect services (the same as in bug Bug 217738, but remote) | ||
* seamless integration with PDE launch. So user will launch his Eclipse Application as usual, but this time views in his host Eclipse will be monitoring the target instance. Next step into better introspection :D | * seamless integration with PDE launch. So user will launch his Eclipse Application as usual, but this time views in his host Eclipse will be monitoring the target instance. Next step into better introspection :D | ||
| + | * when I change something in plugin in workspace, self-hosted instance automatically updates plug-in | ||
| + | |||
| + | |||
| + | Requirements: | ||
| + | * "probe" should work with any targets (Eclipse >=3.2/Equinox/OSGi), to be useful for testing, | ||
| + | * be minimal and simple. No external dependencies. To simplify installation for unexperienced user. There is jmx, ecf, p2, but this all should rather be as simple and flexible as JUnit tests (=click to go). | ||
| + | * should be extensible. To support future ideas. | ||
| + | |||
| + | === Developers === | ||
| + | * Chris Aniszczyk | ||
| + | * Jacek Pospychala | ||
| − | + | === Plug-ins === | |
| − | * | + | * org.eclipse.pde.ui.runtime |
| − | * | + | * org.eclipse.pde.runtime.probe |
| − | + | ||
| − | + | ||
| − | + | === Resources === | |
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 08:29, 6 August 2008
Work Area
Better integrate cooperation between Eclipse host and running instance in self-hosting.
Project overview
see also bug198189
Developer will have a better control over and insight into his running Eclipse/Equinox/OSGi instance
Features:
- Remotely observe and manage instance bundles
- Install bundles in target instance from host workspace
- Follow instance logs in host environment
- inspect services (the same as in bug Bug 217738, but remote)
- seamless integration with PDE launch. So user will launch his Eclipse Application as usual, but this time views in his host Eclipse will be monitoring the target instance. Next step into better introspection :D
- when I change something in plugin in workspace, self-hosted instance automatically updates plug-in
Requirements:
- "probe" should work with any targets (Eclipse >=3.2/Equinox/OSGi), to be useful for testing,
- be minimal and simple. No external dependencies. To simplify installation for unexperienced user. There is jmx, ecf, p2, but this all should rather be as simple and flexible as JUnit tests (=click to go).
- should be extensible. To support future ideas.
Developers
- Chris Aniszczyk
- Jacek Pospychala
Plug-ins
- org.eclipse.pde.ui.runtime
- org.eclipse.pde.runtime.probe