|Re: [virgo-dev] Equinox Console|
I attached a patch for the new console to https://bugs.eclipse.org/bugs/show_bug.cgi?id=351328. I had some problems with installing the build tools from the locally built update site. Could you check if the patch is working? It builds successfully.
Whoops, originally sent this to the wrong Lazar! Sp please note that address below is incorrect -- and direct any replies to the addresses above.
Begin forwarded message:
From: Miles Parker <miles.parker@xxxxxxxxxxx>
Subject: Re: [virgo-dev] Equinox Console
Date: 2 July, 2012 10:24:26 AM PDT
Sorry, I meant 3.5.0, not 3.5.1. If Lazar can do this real soon now than we'll hold 3.5.0.
On 2012-07-02, at 10:22 AM, Miles Parker wrote:
I just realized that this is exactly the same bug that Lazar is addressing in:
Don't know why I didn't put that together in my mind earlier. Lazar, yep, you're on the critical path here. We're going to hold the 3.5.1 solution for this, and thanks very much for your efforts. Let me know what I can do to help.
On 2012-07-02, at 6:53 AM, Glyn Normington wrote:
On 2012-07-02, at 7:56 AM, Kirchev, Lazar wrote:
In 3.5.0 the vsh commands use the format vsh:<command_name> <subcommand> <parameters>, e.g. vsh:bundle start 123. In 2.1.1 the format used to be vsh bundle start 123.
However, the on the console you can call also start 123 – but it will call another shell command, not the vsh’s one. It just happens that there is a start shell command.
Got it. I was clear on the two regions, but they layout wasn't clear to me. So I take it that repository/ext -> User and Configuration -> kernel.
Now, on another question that I probably should have asked before now, has the equinox console syntax changed at some point, e.g. between 2.1.1 and 3.5.0? We're having trouble with the console interaction, which seems to be sending bare commands, e.g. "start 123" as opposed to "vsh:bundle start 123" and I'm not sure how htat would ever have worked.
On 2012-06-28, at 5:52 PM, Glyn Normington wrote:
Good question! There are two instances of configuration admin in Virgo: one for the kernel and one for the user region. Think of a region as a partition of the bundles in a framework with controlled sharing between regions. osgi.console.properties occurs twice because there is a shell for each region. But the web integration layer occurs only in the user region. Hope that makes sense now.