| Summary: | Equinox Console Extension not available | ||
|---|---|---|---|
| Product: | [RT] Virgo | Reporter: | chrisatpinguin <c.wiejack> |
| Component: | unknown | Assignee: | Steve Powell <zteve.powell> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | trivial | ||
| Priority: | P3 | CC: | k2eric, zteve.powell |
| Version: | unspecified | ||
| Target Milestone: | 2.1.0.M05-incubation | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
chrisatpinguin
Thank you for reporting this bug. The documentation contains some errors: first of all (for your problem) it doesn't mention that the relevant property (set in the file org.eclipse.virgo.kernel.userregion.properties in config/) is osgi.console=2401, and we currently ship with this commented out -- that is, with the osgi console >not< enabled. Simply uncomment this to enable the osgi console, and the extensions should be there automatically. Secondly, the doc also refers to the shell (and shell.port parameters). The shell was part of dm Server, and has not survived the transition to an Eclipse Project (for various dependency reasons). Therefore we need to correct that part of the documentation. (The shell commands themselves are moved to being osgi extensions -- those now accessed by the vsh command.) Please can you respond here if I have correctly identified the problem, and we will keep this Bugzilla open (possibly renaming it) to track the documentation errors? Hi, yes you correctly identified the problem. After enabling the line in the config the console was available. Thx for help I have made some changes to the user-guide to explain about the Equinox console and enabling it. That should address this issue -- thank you for raising it. Changes to user-guide made in org.eclipse.virgo.documentation.git under commit 2aff3f... RC1 is planned instead of milestone 5. |