Hi,
When you run with eclipse configuration do you specify the –console option? If it is not specified, the behavior would be exactly as you describe, even if the console bundle and the three gogo bundles are included in the run configuration.
If you set -Dosgi.console.enable.builtin=true, you actually are not using the new console, but the old, pre-gogo shell.
If you want to start equinox with console in this way java -jar equinox-SDK-3.8RC4/plugins/org.eclipse.osgi_3.8.0.v20120529-1548.jar –console you have to add a configuration/config.ini file with osgi.bundles=<equinox_console_and_gogo_bundles> . In this way the framework will start with the new console bundle and the three gogo bundles and you will have the new console.
Regards,
Lazar
From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Raymond Auge
Sent: Thursday, June 14, 2012 1:40 AM
To: Equinox development mailing list
Subject: Re: [equinox-dev] juno drops and gogo
Ok, I finally got it working, with some debugging that lead me to learn you need:
-Dosgi.console.enable.builtin=true
(or set as a Framework property) in order to get a console.
However, unlike previous versions (pre-juno) there is no base shell whatsoever. This means that you cannot interactively install the more advanced gogo shell from the command line.
java -jar equinox-SDK-3.8RC4/plugins/org.eclipse.osgi_3.8.0.v20120529-1548.jar -console
java -jar equinox-SDK-3.8RC4/plugins/org.eclipse.osgi_3.8.0.v20120529-1548.jar -Dosgi.console.enable.builtin=true
The second scenario which is the "new and improved" configuration, which won't actually do anything until there is actually a console bundle implementation available, but you can't install the console bundle(s) because there is no shell.
Wouldn't this make bootstrapping a bare instance impossible?
Can someone correct me on this? Maybe I've missed something.