On Thu, Jun 14, 2012 at 1:36 AM, Kirchev, Lazar <[email protected]> wrote:
> When you run with eclipse configuration do you specify the –console option? > I did, as shown in the previous message. > 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. > Ok, granted. But this is not the case when bootstrapping equinox using the Framework API (embedded). In this mode the EclipseStarter class is never used (which parses the -console arg). The way (as I've discovered) to set it declaratively when using the Framework API is to pass the framework or system property osgi.console -Dosgi.console - with an empty value, e.g. "", gives a shell on in/out, - with a port number - with a host:port to bind on a net interface & port (as long as host is, or resolves to, an local interface) Hope this info is helpful. -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> <http://twitter.com/#!/rotty3000> | Senior Software Architect | *Liferay, Inc.* <http://www.liferay.com> <https://twitter.com/#!/liferay>
_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
